Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] Maven classloader change
To clarify:
With Maven 3.5.1 on CLI, jaxws-maven-plugin uses plexus-utils as declared in it's pom (i.e. v3.0.22 for jaxws-m-p v2.5).
With m2e updated with embedded Maven 3.5.1, jaxws-maven-plugin uses a different version of plexus-utils than the one declared in it's pom. It seems to be v3.1.0 which happens to be the version of plexus-utils included in Maven 3.5.1.

This difference in behavior is not good I think as it could cause different behavior in m2e than on CLI. Is it the intended behavior or is it the MNG-6275 [1] change that causes this in m2e?

My tests show that with m2e 1.8.0 or m2e 1.9.0-SNAPSHOT (Maven 3.5.0) the plugin's pom dependencies are honored. With m2e 1.9.0-SNAPSHOT with Maven 3.5.1 embedded that changes which I would guess is due to MNG-6275.

My guess is that the issue with jaxws-maven-plugin we're seeing is just one exemple of problems caused by this. So my question is if it is possible to change m2e to handle MNG-6275 or if we should vote -1 on that change? I don't have that m2e knowledge so I would very much appreciate if someone else could answer that.

/Anders

 

Please note that this specific library difference might not be the root cause for the jaxws-m-p issue.

Please note that we need to respond to the vote before 13:00 UTC if m2e is having a problem with the class loader change.


/Anders

 

/Anders

On Fri, Sep 15, 2017 at 9:24 AM, Anders Hammar <anders@xxxxxxxxxx> wrote:

On Fri, Sep 15, 2017 at 9:14 AM, Thorsten Heit <thorsten.heit@xxxxxx> wrote:
Hi Fred,

> That doesn't look like an m2e issue. Did it work before you installed m2e 1.9.0?
> I can't repro on Oxygen Java EE.
>
> Please try on a clean Eclipse install.

Indeed, with a vanilla Eclipse Oxygen JEE installation (via Eclipse installer) this works.
Obviously there are some changes between 4.7.0 and the upcoming 4.7.1 that will cause this (mis-?)behaviour in m2e 1.9.0...

This is strange. I'm seeing the issue with a clean Eclipse 4.7.0 (Java developer packaging installed with Eclipse Installer) which I just update with m2e 1.9.0 build with Maven 3.5.1 embedded.

/Anders

 


Regards

Thorsten
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev




Back to the top