Delete mojohaus/gwt-maven-plugin

Skip to first unread message

Ignacio Baca Moreno-Torres

Jul 10, 2015, 1:43:55 AM7/10/15
Currently there are two repositories for this plugin in github.

The mojohaus one is obsolete. It's possible that mojohaus team end up migrating the old issues from jira to this repo (not sure if this is useful), and most of the mojohaus sub-projects are pointing it's maven site to this mojohaus gh-pages (but I suppose that this pages can be placed anywhere). If no one has any complain about deleting this repository, we will delete.

In the mean time, we are going to deploy the last release maven site to gwt-maven-plugin/gwt-maven-plugin (currently last snapshot), and try to modify mojohaus site to point to this new location (instead of mojohaus/gwt-maven-plugin).

Thomas Broyer

Jul 10, 2015, 11:24:04 AM7/10/15
Let's lay things down:

  • mojohaus/gwt-maven-plugin:
    • is where people used to CodeHaus Mojo (those using the plugin but never contributed or even looked at its code) will go looking at to report issues
    • has its gh-pages available at
      IFF MojoHaus eventually change their redirection rules from to preserve the requested path, then all the old links would come back to life
      People used to CodeHaus mojo will also naturally try to just change to to try to read the docs (I've actually had an edit in StackOverflow where the editor did just that, without even checking whether the new link actually worked).
      Having the website under makes it clean that this is a MojoHaus project. I don't know if it has any weight in the balance, but I thought I'd just throw this here anyway.
  • gwt-maven-plugin/gwt-maven-plugin:
    • is known to all people having looked at the code and/or contributed patches
    • is next to other projects related to it in the gwt-maven-plugin organization (those projects appear long dead though; last update 4 years ago)
    • there are really few links to it out there (compared to links to the old JIRA for issues, or the old doc at
I think that when you rename/move/transfer-ownership of a project in GitHub, they automatically do a redirect. So it would probably be possible to delete the repo at mojohaus and then transfer the repo from gwt-maven-plugin to mojohaus (maybe first check with GitHub support).

Or the mojohaus repo could be emptied, with just a README linking to the "real" code repo, and with wiki and issues hidden/disabled, and kept only to host the gh-pages so they appear online under

I don't have a strong opinion one way or the other, but I think there are many advantages to having the docs under (particularly IFF they eventually change the redirection rules from to keep the requested path; so maybe check with MojoHaus first about their future intents), and some more to having everything (code and issues) under the mojohaus organization as well.
There are only few drawbacks to killing the gwt-maven-plugin repo (and organization altogether) and moving everything to MojoHaus, maybe the biggest one is managing committers, but I think there's been some changes at GitHub lately such that at least it shouldn't be a showstopper.

It would also be useful to know whether MojoHaus would migrate the old JIRA issues to any repo (provider they're given API access to it), or only to ones that are under the mojohaus organization. That would possibly weigh in the balance.

Oh, and BTW, should that Group be renamed too?


Jul 10, 2015, 12:48:06 PM7/10/15
to odehaus Mojo gwt-maven-plugin Users
All good stuff. However..

I think really the project should be under the mojohaus top level
group. The reason that gwt-maven-plugin/gwt-maven-plugin exists was
because the developers wanted to use git/github. Now that it is a
reality while under the codehaus/mojohaus group, development should be
moved back under the normal codehaus/mojohaus umbrella.
> --
> 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
> To post to this group, send email to
> Visit this group at
> For more options, visit
Reply all
Reply to author
0 new messages