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
Dependency Conflict in upgrading to Maven 3.6.1 #803
Comments
It's hard to see this as a bug when it only exists if we make a modification to the code we haven't made yet. |
This is the part that looks off. If I read this right com.google.cloud.tools:dependencies:jar:0.2.4-SNAPSHOT has direct dependencies on org.apache.maven:maven-core:jar:3.6.0 and org.apache.maven:maven-compat:jar:3.6.1. I expect the versions of these to match.
|
The maven-core's version under
from gist How did you get the output containing "3.6.0" in the dependency tree? |
The problem would be fixed by #802 but the root cause seems deeper than I thought.
Why didn't maven or surefire plugin was not able to build a class path containing Enforcer-rule contains plexus-util 3.1.0 dependency: |
Upgrading maven-core to 3.6.1 failed with following runtime erorors (#802 802):
org.codehaus.plexus:plexus-utils:3.1.0 has org.codehaus.plexus.util.xml.Xpp3DomBuilder without InputLocationBuilder.
org.codehaus.plexus:plexus-utils:3.2.0 has Xpp3DomBuilder.InputLocationBuilder. It's used by maven-compat
The text was updated successfully, but these errors were encountered: