[ANN] (Unofficial) JsInterop-Base 1.0.0-b2-e6d791f release
The jsInterop-base library contains a set of utilities to implement functionality that cannot be expressed with Jsinterop alone. https://github.com/google/jsinterop-base This is an unofficial release to Maven Central under a different groupId. Please don't bug the original authors. Versions are released on demand. The only change relative to 1.0.0-b1-e6d791f is that the java source is included in the main jar rather than only being available in the `-sources` jar. This was to align with behaviour of the original 1.0.0-RC1 release. The Maven dependency can be added to your pom.xml via org.realityforge.org.realityforge.com.google.jsinterop base 1.0.0-b2-e6d791f Hope this helps, Peter Donald -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Seeking advice, migrating from Ant to Maven for GWT App build
On Saturday, February 23, 2019 at 7:31:20 AM UTC-5, Thomas Broyer wrote: > > > Given your description, you *could* create fewer Maven modules (I'm not > saying you should do it, but you could) > * shared, with common.shared, app_a.shared and app_b.shared > * common-client, as a gwt-lib, with common.client, and depending on shared > and shared-sources > * app_a, as a gwt-app, with a dependency on common-client and shared (and > shared-sources), though that one is also brought transitively through > common-client > * app_b, as a gwt-app, with a dependency on common-client and shared (same > as app_a) > * server, as a war, with common.server, app_a.server and app_b.server, and > a dependency on shared. > OK, that makes sense to me. 3 modules for the 3 gwt bits, then a single shared and server module for those bits. I think that would be a viable approach... Note that you could technically also use a single Maven module mixing > client and server code, but this means your server-side dependencies are in > your client code classpath (compile and "runtime"), and your client-side > dependencies are in your server compile classpath (not runtime if you > correctly exclude them from your WAR). If that's how you manage your > classpaths with Ant, then it could provide an easier migration path to > Maven; see > https://github.com/gwtproject/gwt/blob/2.8.2/user/src/com/google/gwt/user/tools/templates/maven/pom.xmlsrc > > for an example setup (this is the template used by GWT's WebAppCreator) > I feel like using your plugin, then glomming everything into single maven module wouldn't be a prudent approach. I see the inherent benefit of the multi-module structure, just didn't want to deal with the module-bloat that would have occurred in our app with the approach I was considering (you're 5 module suggestion make a lot more sense to me though). BTW - my main reason for wanting to move to a maven-based build is to >> manage the dependent jars in the web-inf/lib directory. >> > > If that's your main driver and you're otherwise OK with Ant, then maybe > have a look at Ivy. > I haven't been looking at build systems for the past few years and apparently completely missed Ivy. It does look to be exactly what I'm really looking for in this case. Thanks so much for the pointer! I think you've got me pointed in the right direction. For this situation it's looking like Ivy is probably the right answer for us at this time. Thanks so much for taking the time to reply! -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Seeking advice, migrating from Ant to Maven for GWT App build
On Saturday, February 23, 2019 at 12:55:17 PM UTC+1, Ralph Roland wrote: > > I'm considering migrating an existing application from being built with > Ant, to being built with Maven. > I've been doing a lot of reading and experimenting with the > net.ltgt.gwt.maven gwt-maven-plugin but can't seem to wrap my head around > the specifics of moving our existing application to the multi-(maven)module > model recommended for this plugin. > This application is really two apps in one (each with a separate > EntryPoint) plus a third 'common' gwt-module plus supporting common java > classes, etc. Both App-A and App-B GWT modules "inherit" the Common GWT > module. Finally a separate control servlet acts the front-end and returns > HTML invoking the correct GWT javascript (App-A or App-B) based on the > requested URL. > > Our current project structure is: > Project >src > com > foo > app_a >client > >AppAEntryPoint.java >server > >shared > >App_A.gwt.xml > app_b >client > > AppBEntryPoint.java >server > >shared > >App_B.gwt.xml > common >client > >server > >shared > >Common.gwt.xml (no defined) >war > WEB_INF > lib > > My best guess right now for migrating the structure would be to break this > into 3 separate projects (App-A, App-B and Common) each with 3 maven > modules (App-A-client, App-A-Server, App-A-shared, App-B-client, etc...) > But this seems a bit extreme in that we would end up with 12 distinct > Eclipse projects, with code 'spread' across 9 of those. I feel like if > App-A and App-B didn't have their own EntryPoints that I could easily > transform this to fit the multi-module archetype structure, but the > multiple EntryPoints keeps tripping me up. > > Is there something obvious (or not) that I'm missing that would allow our > app to 'live' in the (relatively simple) archetyped structure? > Given your description, you *could* create fewer Maven modules (I'm not saying you should do it, but you could) * shared, with common.shared, app_a.shared and app_b.shared * common-client, as a gwt-lib, with common.client, and depending on shared and shared-sources * app_a, as a gwt-app, with a dependency on common-client and shared (and shared-sources), though that one is also brought transitively through common-client * app_b, as a gwt-app, with a dependency on common-client and shared (same as app_a) * server, as a war, with common.server, app_a.server and app_b.server, and a dependency on shared. Note that you could technically also use a single Maven module mixing client and server code, but this means your server-side dependencies are in your client code classpath (compile and "runtime"), and your client-side dependencies are in your server compile classpath (not runtime if you correctly exclude them from your WAR). If that's how you manage your classpaths with Ant, then it could provide an easier migration path to Maven; see https://github.com/gwtproject/gwt/blob/2.8.2/user/src/com/google/gwt/user/tools/templates/maven/pom.xmlsrc for an example setup (this is the template used by GWT's WebAppCreator) BTW - my main reason for wanting to move to a maven-based build is to > manage the dependent jars in the web-inf/lib directory. > If that's your main driver and you're otherwise OK with Ant, then maybe have a look at Ivy. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Annotation processing in Eclipse
On Friday, February 22, 2019 at 8:40:27 PM UTC+1, Lars wrote: > > Dagger does not play well with the incremental compiler of eclipse - see > https://stackoverflow.com/questions/41178320/does-dagger2-annotation-processor-supports-the-eclipse-incremental-compiler > Background is, that the standard annotation processor does only know > things from the current runs and this is limited (by design) for an > incremental compiler. Whitout some additional (non-standard) components to > see the full code or to give the compiler more hints for the dependencies > for the generated classes, this works only with a full compile. Dagger works great with Gradle incremental compilation and annotation processing, so it's not a problem of incremental compilation/processing per se, but likely the bugs that litter the Eclipse compiler (see Jens' answer). Eclipse annotation processing is known to be broken in many ways, though things are getting better with each release, so first make sure you use the very latest version of Eclipse. You may want to disable "in the editor" processing and explicitly run annotation processing by rebuilding the project (or something like that; I haven't used Eclipse for years, and I don't let my IDE do anything build-related so 🤷) -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Seeking advice, migrating from Ant to Maven for GWT App build
I'm considering migrating an existing application from being built with Ant, to being built with Maven. I've been doing a lot of reading and experimenting with the net.ltgt.gwt.maven gwt-maven-plugin but can't seem to wrap my head around the specifics of moving our existing application to the multi-(maven)module model recommended for this plugin. This application is really two apps in one (each with a separate EntryPoint) plus a third 'common' gwt-module plus supporting common java classes, etc. Both App-A and App-B GWT modules "inherit" the Common GWT module. Finally a separate control servlet acts the front-end and returns HTML invoking the correct GWT javascript (App-A or App-B) based on the requested URL. Our current project structure is: Project src com foo app_a client AppAEntryPoint.java server shared App_A.gwt.xml app_b client AppBEntryPoint.java server shared App_B.gwt.xml common client server shared Common.gwt.xml (no defined) war WEB_INF lib My best guess right now for migrating the structure would be to break this into 3 separate projects (App-A, App-B and Common) each with 3 maven modules (App-A-client, App-A-Server, App-A-shared, App-B-client, etc...) But this seems a bit extreme in that we would end up with 12 distinct Eclipse projects, with code 'spread' across 9 of those. I feel like if App-A and App-B didn't have their own EntryPoints that I could easily transform this to fit the multi-module archetype structure, but the multiple EntryPoints keeps tripping me up. Is there something obvious (or not) that I'm missing that would allow our app to 'live' in the (relatively simple) archetyped structure? BTW - my main reason for wanting to move to a maven-based build is to manage the dependent jars in the web-inf/lib directory. Thanks in advance for any pointers! -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Has anybody found a reasonable way to convert *.ui.xml files to web components.
We have many angular developers on the team and they would like to begin to migrate a legacy GWT application (2.7.x) to an NG based application. RPC has already been replaced using resty-gwt; so now the objective is to begin migrating the client from GWT to Angular. Has anyone found an tools to help convert UIBinder widgets/screens into web-components. We started by look for gwt compiler options to generate separate html, js, and html files for each *.ui.xml; but there are no such options.We did find options to generated the bundle sources via -gen/etc.; however these are obviously precompile output used to generate the final js file used to implement the client. Any ideas or suggestions would be greatly appreciated!! Thank you. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
[ANN] (Unofficial) JsInterop-Base 1.0.0-b1-e6d791f release
The jsInterop-base library contains a set of utilities to implement functionality that cannot be expressed with Jsinterop alone. https://github.com/google/jsinterop-base This is an unofficial release to Maven Central under a different groupId. Please don't bug the original authors. Versions are released on demand. This release contains 2 breaking changes. The removal of the methods: * JsArrayLike::getAnyAt(int) * JsPropertyMap::getAny(java.lang.String) And 6 non breaking changes. It should be noted that this is the GWT2.x variant and is not j2cl compatible. In the future there may be a j2cl compatible artifact released if there is demand. The Maven dependency can be added to your pom.xml via org.realityforge.org.realityforge.com.google.jsinterop base 1.0.0-b1-e6d791f Hope this helps, Peter Donald -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
