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 fi
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 wrote:
> It should be the first one specified in pluginManagement
>
> Robert
>
> Op Wed, 07 Oct 2015 23:38:10 +0200 schreef Dan Tran :
>
>> Just wonder
>>
>> after the migra
yes if nothing is specified in pluginManagement, maven will look into apache
groupId firstly and in mojo groupId in a second time
That’s why releasing a latest dummy version on apache side announcing the move
may be a good idea for all people using it to invite us to specify the required
entry i
Some goals can run outside of maven project. Very likely apache one will be
first.
-D
On Wednesday, October 7, 2015, Robert Scholte wrote:
> It should be the first one specified in pluginManagement
>
> Robert
>
> Op Wed, 07 Oct 2015 23:38:10 +0200 schreef Dan Tran :
>
> Just wonder
>>
>> after
It should be the first one specified in pluginManagement
Robert
Op Wed, 07 Oct 2015 23:38:10 +0200 schreef Dan Tran :
Just wonder
after the migration
which plugin would (apache, codehaus)
mvn eclipse:
picks up?
Thanks
-Dan
On Wed, Oct 7, 2015 at 12:22 PM, Robert Scholte
wrote:
Just wonder
after the migration
which plugin would (apache, codehaus)
mvn eclipse:
picks up?
Thanks
-Dan
On Wed, Oct 7, 2015 at 12:22 PM, Robert Scholte
wrote:
> Hi,
>
> as one might already have read: the Apache Maven team has decided to stop
> the maintenance of the maven-eclipse
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
