On Wednesday, January 15, 2020 at 3:49:34 AM UTC-5, Thomas Broyer wrote:
>
> IIRC, with Super Dev Mode, public artifacts aren't generated in the
> launcher dir; you need to build your path relative to
> GWT.getModuleBaseForStaticFiles()
>
Gradle is used in another package in this project, but not in the package
where I'm trying to do a GWT Compile; this package doesn't use gradle at
all.
I do see reports of this same internal gradle exception in recent Eclipse
distributions:
https://github.com/eclipse/buildship/issues/943
Atm the community is very active. We are working on GWT modules: replacing
generators and JSNI, testig the migraed moules against J2CL, etc.
Besides that, many new frameworks are evolving.
Take a look at this rooms:
https://gitter.im/gwtproject/gwt
https://gitter.im/vertispan/j2cl
You should ask this question here: https://gitter.im/gwtproject/gwt
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I think I figured it out. I am using a reverse proxy to front both the website
delivering the gwt application and the codeserver. The reason for this is
because our application requires SSL and I cannot easily switch it off. I based
this reverse proxy on example code DevServer from Thomas
