I'm about to put out a blog post with a bunch of details on how one might port gwt-user.jar modules out (thanks to the hard work of those who have started this effort already, especially Dan Kurka and Thomas Broyer), and once those are ready to be consumed, we'll certainly want the various artifacts on maven central. The goal in this is to start motivating contributors and community members to assist in the migration work necessary to get us within reach of a GWT 3 ecosystem.
The topic of "where we deploy early efforts" has come up a few times behind relatively closed doors - multiple times in steering calls, and of course at length at GwtCon this year. So, opening it up for broad discussion: should we expect to start pushing release to org.gwtproject.* right away, and if not, are we encouraging individual contributors to push to their own groupIds until we *are* ready? Case for org.gwtproject: "centralized" jenkins server with creds to push, making it easy to add a project (automatically?) and get it out there so others can use it. Might want some manual checks on what is going out (or else whoever is responsible for the groupId will look silly if it turns out we are shipping malware), which implies full or partial review (manual process) of each release before pushing the button. Makes it clear right away to people searching maven central that they have found the right new modules, since they are all under the org.gwtproject umbrella. Case for individual groupIds: makes it clear to early adopters that these are "incubator" projects, and they should probably vet them themselves, or they are relying on the community and goodwill of other developers, and that these migrated modules are *not* official - at least not yet. Lower friction, gets snapshots and releases out faster. No matter how we go, I am certain that we'll want to push to org.gwtproject once these modules are stabilizing and we (gwt maintainers and contributors) are confident in the code being shipped. Thoughts? Which ever way we go, I'd like to see the already ready-for-use artifacts deployed within a few days - if that is too soon for org.gwtproject, then I think that makes the choice clear, or else who knows how long we'll be waiting. -- 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-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/88b63997-3178-4d63-9f32-61cf531461c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.