Your comments

Unfortunately, things are not that easy for me in the communication with my management.

In my company I have acceptance issues with GWT's long compile times (if you are a background developer, which is the majority of the developers).

I told them: "With GWT 3.0 we will have a 'blazing fast' J2Cl transpiler. "

The next question is: "When will it be available?"

Then I have to tell them: "I don't know."

"Will it be a year, 2 years or who guarantees that it will show up at all?"

"I don't know"

Therefore my management will consider GWT a dead horse and will abandon GWT (which I would regret very much).

But I have no real argument against such a decision, because I have not even a clue about the time frame, when GWT3.0 will show up. And since this is not available, management is not really keen on investing in preparing for GWT 3.0.

I think Daniel Kurka mentioned in last years GWTCon that J2Cl was already piloted within Google.

But in this year's conference no one from Google is showing up at all.

If I compare GWT road map announcements with Angular2 it is pretty different. Angular2 always announced it was coming and it took years until the final release was available. And people waited patiently for it. I am not convinced this will be the case with GWT, too.

I have currently no experience with APT.

I am not sure how you can replace the "JClassType[] com.google.gwt.core.ext.typeinfo.TypeOracle.getTypes()", which we currently use extensively in our code generators.

Is it possible to have something similar?

Do you know of any implementation patterns, which could replace the need to know all classes?