Re: [m2e-users] Eclipse facets - Project nature

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

That's exactly the problem. There is no way to know for sure if m-e-p
conflicts with various m2e extensions. We started to explicitly block
m-e-p from projects managed by m2e when we realized that we were
spending noticeable time troubleshooting incompatibilities.

If you have specific use case I think it is far more productive to
discuss how to support this usecase in m2e directly, instead of trying
to find a way to use both m2e and m-e-p together on the same project.

--
Regards,
Igor

On 11-06-17 9:50 PM, Philippe Bastiani wrote:
> Igor,
>
> Yes, I know this...but sometimes we cannot choose between the 2 plugins !
>  From my point of view, M2E offers the best solution since it is fully
> integrated to Eclipse...
>
> At the present time, to start with M2E, I proceed as the following:
> -1- creation of a new Eclipse project with eclipse:goal goal of
> maven-eclipse-plugin,
> -2- adding the M2Eclipse project nature,
> -3- removing of useless Eclipse dependances,
> -4- updating the M2E project configuration.
>
> I do not know if the steps 1&2 retrieve all the configuration of my POMs.
> In other word:  are there conflicts with the M2E extensions (WTP, AJDT,
> Checkstyle, ...) ?
>
> In all cases, the maven plugin still seems necessary to preserve the
> specific configuration Eclipse (project nature&  launchers, ...): if I'm
> right, this means that we need maintain a 'fake' configuration of the maven
> plugin !
>
> Regards,
> Philippe