I would go even further here.
The Eclipse <-> Maven integration is still (2015!) hugely messy, often
requiring special hacks within Mojos to work [at all].
M2E - which seems like the preferred choice in the Eclipse community -
depends on largely undocumented hacks to
work with Mojos updating file systems and other IDE/Maven-related
properties.
For example - I still don't know how to make ITs within a Mojo codebase to
validate that M2E gets whatever data
it needs to work properly.
It seems that the Eclipse community requires less entropy to get their
Maven integration to work properly - not more.
Hence, I would recommend *not adding* the Eclipse Maven plugin to Mojohaus
unless someone is actually prepared
to work with it and maintain it. We already have a lot of plugins, and
adding yet another rarely-if-ever-used mojo to
our collection does not seem to assist in creating simplicity for
developers out there.
("Focus on the living, not the undead").
My 2 cents.
Den fredag 9 oktober 2015 kl. 13:19:24 UTC+2 skrev Jochen Wiedmann:
>
> Given the low likelyhood of another release: I don't think we need to
> care.
>
>
> On Thu, Oct 8, 2015 at 6:03 PM, Robert Scholte <rfsc...@apache.org
> <javascript:>> wrote:
> > It should be the first one specified in pluginManagement
> >
> > Robert
> >
> > Op Wed, 07 Oct 2015 23:38:10 +0200 schreef Dan Tran <dan...@gmail.com
> <javascript:>>:
> >
> >> 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 <rfsc...@apache.org
> <javascript:>>
> >> 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-uns...@maven.apache.org <javascript:>
> >>> For additional commands, e-mail: dev-...@maven.apache.org
> <javascript:>
> >>>
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups
> > "mojohaus-dev" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an
> > email to mojohaus-dev...@googlegroups.com <javascript:>.
> > To post to this group, send email to mojoha...@googlegroups.com
> <javascript:>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/mojohaus-dev/op.x55n4ry2kdkhrr%40robertscholte.dynamic.ziggo.nl.
>
>
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> The next time you hear: "Don't reinvent the wheel!"
>
>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
