First org.gwtproject.* modules published to Central

222 views
Skip to first unread message

Thomas Broyer

unread,
May 22, 2020, 6:08:34 PM5/22/20
to GWT Contributors
Hi all,

I updated gwt-http, gwt-events, gwt-window, gwt-history, and gwt-places to GWT 2.9.0 and Elemental2 1.0.0, and just released 1.0.0-RC1 versions of each of them.
Time to test and report any issues with them:

Stanislav Spiridonov

unread,
May 24, 2020, 12:02:32 PM5/24/20
to GWT Contributors
Congratulation!

Stas

Filipe Sousa

unread,
May 24, 2020, 1:44:17 PM5/24/20
to GWT Contributors
👏

Vassilis Virvilis

unread,
May 25, 2020, 3:24:33 AM5/25/20
to google-web-tool...@googlegroups.com
Congrats Thomas and to any other if involved in this.

I skimmed the repositories a little bit.

Can you please reiterate or confirm a bit the porting strategy?

My understanding is that:
  • these projects/classes are builtin in GWT 2.9
  • but there will be no more in GWT 3.0 so we need to include them as separate projects when we will make the switch to GWT 3 with minimal source changes.
Is it possible to start preparing now with GWT 2.9 before GWT 3? Maybe if we drop gwt-user from the dependencies and include these mini gwt-project* ? Or it is not supposed to work like that?

  Vassilis




--
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/9d202c46-e1ba-49ef-8144-881a9c50555b%40googlegroups.com.


--
Vassilis Virvilis

Jens

unread,
May 25, 2020, 3:46:44 AM5/25/20
to GWT Contributors
My understanding is that:
  • these projects/classes are builtin in GWT 2.9
Their old, non J2CL compatible versions are buildin in GWT 2.9. No changes are made here.
 

 
Is it possible to start preparing now with GWT 2.9 before GWT 3? Maybe if we drop gwt-user from the dependencies and include these mini gwt-project* ? Or it is not supposed to work like that?

gwt-user code is still in package com.google.gwt while the package for the various small gwt-* projects is org.gwtproject. So you would add the small projects to your class path and then update your imports in your project to point to the new classes / projects. 

You would continue to do that with all the other upcoming gwt-* projects until your projects does not use any com.google.gwt imports anymore. Then you can drop gwt-user.jar. 

The projects above should be relatively easy to integrate into your app. Maybe gwt-events needs a little more work since you generally want your own custom events to move away from GwtEvent / EventHandler as both are not required.


-- J.

Vassilis Virvilis

unread,
May 25, 2020, 4:03:38 AM5/25/20
to google-web-tool...@googlegroups.com
Jens,

That makes perfect sense. Thank you.

I hadn't notice the package name change. This allows same functionality classes to coexist and allows for gradual transition.

  Vassilis

--
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.


--
Vassilis Virvilis

Thomas Broyer

unread,
Jul 31, 2020, 8:26:57 PM7/31/20
to GWT Contributors
FYI, gwt-http and gwt-window have had a 1.0.0-RC2 recently that bring J2CL compatibility (and on GWT2 side add META-INF/gwt/mainModule for use with the gwt-maven-plugin's generate-module goal).


On Saturday, May 23, 2020 at 12:08:34 AM UTC+2, Thomas Broyer wrote:
Reply all
Reply to author
Forward
0 new messages