Just wonder
after the migration
which plugin would (apache, codehaus)
mvn eclipse:xxxx
picks up?
Thanks
-Dan
On Wed, Oct 7, 2015 at 12:22 PM, Robert Scholte <rfscho...@apache.org>
wrote:
> Hi,
>
> as one might already have read: the Apache Maven team has decided to stop
> the maintenance of the maven-eclipse-plugin. Even though M2Eclipse does a
> great job, some still prefer or need to use the maven-eclipse-plugin.
> For this reason the plugin is donated to Mojohaus.
>
> I've done a check on the svn history and there is no relevant change after
> the 2.10 release.
>
> Before completely removing it from Apache source repository we need to
> move the code.
> Based on the naming convention the plugin should be renamed to
> eclipse-maven-plugin.
> The package should also be renamed, which won't have any impact on the
> working of the plugin.
>
> On the Apache Maven site we probably need to do a final release (2.99 ?)
> My idea (or actually Arnauds) is to let all goals throw a
> MojoFailureException. The message should refer to both m2eclipse and the
> eclipse-maven-plugin at mojohaus. It should have the instructions on how
> you can still use eclipse:eclipse
>
> If there are other things we need to take into account or subjects/ideas
> to help migrating this project, please respond to this thread.
>
> regards,
> Robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
