-
Notifications
You must be signed in to change notification settings - Fork 181
[MDEP-717] Upgrade to 3.1.1 #78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There's a really nasty diamond dependency problem in the tree. We're pulling in asm:asm:3.3.1 and org.ow2.asm:asm:jar:8.0.1. You can see this in integration test failures. |
Here's the problematic path:
Can we exclude asm:asm or push the plugin api higher? |
Excluding asm:asm causes a lot of this: [ERROR] Errors: |
Adding an extra dependency <dependency>
<groupId>org.eclipse.sisu</groupId>
<artifactId>org.eclipse.sisu.inject</artifactId>
<version>0.0.0.M3</version>
</dependency> gets rid of asm:asm but causes lots of
|
Going to 3.1.1 instead of 3.1.0 seems to work. |
Please check release note for 3.1.1 - there was one bug fixed to exclude a dependency |
This passes. I wish I had tried this simple fix earlier. Any objections to making 3.1.1 the minimum? |
This is probably a result of https://issues.apache.org/jira/browse/MNG-5499 which was fixed in 3.1.1 |
* use Maven 3.1.1
@ian-lavallee @rfscholte This upgrades the plugin to Maven 3.1 minimum with no org.sonatype classes.