PSA: CodeHaus is shutting down. Call for volunteers.

[Thomas Broyer]

If you haven't seen the news yet, CodeHaus is closing its doors: http://www.codehaus.org/

The CodeHaus Mojo team is planning the move of mojo.codehaus.org-related projects: http://markmail.org/thread/gnn6ko7rd36oerae

gwt-maven-plugin had already moved to GitHub and Google Groups, but kept using JIRA for issues and Nexus for deployments.

Nexus shouldn't be too much of a problem (the Mojo team will sort it out), but I'm not willing to invest any time moving issues from JIRA to GitHub.

I will however happily grant people the needed rights to do so if there's any volunteer.

Before doing that though, I suggest that we wait a bit to see what the Mojo team will propose. Don't expect me to track this though; I'll possibly get the news through Twitter but won't go looking after it. If you're interested in the future of the gwt-maven-plugin, please come contribute time to help make the final move.

In brief: this is a call for volunteers to (a) track what the Mojo team will decide, and (b) move JIRA issues depending on the outcome of (a).

[Jeff MAURY]

You can get JIRA Cloud for OSS projects

Jeff

--
You received this message because you are subscribed to the Google Groups "Codehaus Mojo gwt-maven-plugin Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codehaus-mojo-gwt-maven-...@googlegroups.com.
To post to this group, send email to codehaus-mojo-gwt-...@googlegroups.com.
Visit this group at http://groups.google.com/group/codehaus-mojo-gwt-maven-plugin-users.
For more options, visit https://groups.google.com/d/optout.

--

Jeff MAURY


"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury

[Brandon Donnelson]

What's needed yet to be done besides the issues?

[Thomas Broyer]

FWIW, CodeHaus Mojo is now MojoHaus and hosted on GitHub: http://markmail.org/message/nryljpeqswjagxel

They moved the old SVN repo to https://github.com/mojohaus/gwt-maven-plugin I don't know what would be best: delete that repo (or possibly push some README linking to https://github.com/gwt-maven-plugin/gwt-maven-plugin) or "migrate" https://github.com/gwt-maven-plugin/gwt-maven-plugin to the MojoHaus organization (that'd be a good idea I think if they decide to move issues to GitHub eventually). There are other projects in the gwt-maven-plugin organization, I have no idea what their status is; but there's now a GWT Plugin for Eclipse (forked from the Google Plugin for Eclipse) at https://github.com/gwt-eclipse-plugin, that also hosts the GWT Designer; so it might be best to merge projects (or abandon the ones in the gwt-maven-plugin organization).

AFAIK, issues have not yet been migrated anywhere; and Nexus won't close (it's hosted in a different infra)

If you're interested, follow (or participate in) the discussion on https://groups.google.com/forum/#!forum/mojohaus-dev

BTW, reviewing http://www.mojohaus.org the other day, I'll rename the plugin from "GWT Maven Plugin" to "Mojo's Maven Plugin for GWT" to comply with the MojoHaus naming rules.

I'll also update outdated links to developers.google.com to point to gwtproject.org.

[Brandon Donnelson]

Does renaming it mean the artifact name changes? If so that will create some issues with Eclipse IDE. 

I created the GWT Eclipse Plugin, so that is a possibility to do some merging. If a merge happened, I might rename the parent github so it doesn't have eclipse in the name. I'm down for the GWT meetup, so I'll ask what the other guys think too. 

Thanks,

Brandon

[Thomas Broyer]

No, it's only about branding (and already done in the repo)

[Colin Alworth]

It looks like the mojo documentation has vanished with the demise of mojo.codehause.org - Google still points at mojo.codehaus.org/gwt-maven-plugin when searching for gwt-maven-plugin, but nothing is there. 

I also looked at http://www.mojohaus.org/, which does indicate that the transition is still ongoing, and http://www.mojohaus.org/plugins.html lists GWT (2.6.0 though), but the link is dead. Is the plan for the 2.7+ site docs to be deployed there, or will these go to the gwt-maven-plugin.github.io domain instead?

[Colin Alworth]

Whoops, just found https://groups.google.com/d/msg/google-web-toolkit/g1pzfuLGO-M/3RTT8WuPX90J. I'll generate the site and put up a patch on the github side, if the politics/signup of getting it into mojohaus are fairly straightforward, I volunteer to take that on as well going forward.

[Brandon Donnelson]

Cool. Thanks Colin. 

[Ignacio Baca Moreno-Torres]

Some one which has access to the old codehaus repository must request new creadentials in this thread https://groups.google.com/forum/#!topic/mojohaus-dev/-3DXyqeojOQ. This is required to deploy to nexus.codehaus.com which is currentlu not working (old credentials has not been migrated). Thanks. 

On Friday, February 27, 2015 at 12:24:50 PM UTC+1, Thomas Broyer wrote: