Incompatibilty with maven 3.5.1 and earlier #1054
Comments
|
We are experiencing similar issues with Maven 3.2.2. Upgrading to 3.5.2, as suggested by @WaatzeG, seems to fix the problem. |
|
Thanks for the bug report... I'll see what can be done to resolve this. |
|
Hello everyone, |
|
I've also confirmed this to be an issue with Maven 3.3.9. The issue also appears in Maven 3.1.0 which is the minimum Maven version supported. The issue has surfaced between ODC 3.0.2 and 3.1.0. ODC 3.0.2 does not have this issue. |
|
@stevespringett thanks for the analysis! I'll try to see what changed on the Maven side between these two. |
|
Looking at the changes I'm guessing it has to do with a version upgrade on Which was upgraded to <plugin>
<groupId>org.owasp</groupId>
<artifactId>dependency-check-maven</artifactId>
<version>3.1.0</version>
<configuration>
<centralAnalyzerEnabled>false</centralAnalyzerEnabled>
</configuration>
<dependencies>
<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-artifact-transfer</artifactId>
<version>0.9.0</version>
</dependency>
</dependencies>
<executions>
<execution>
<goals>
<goal>check</goal>
</goals>
</execution>
</executions>
</plugin> |
|
@WaatzeG Please rename the topic of this isse to "Incompatibilty of Dep. Check 3.1.0 with maven 3.2.X/3.3.X (possibly other versions too)" to be able to identify the isssue fast by others. I've also confirmed an issue with Maven 3.2.5. In addition, this issue is only related to 3.1.0 (as you can see in the post of @jeremylong). |
stevespringett
changed the title
|
@jeremylong Hello all, I have just tried in a pom with |
WaatzeG
changed the title
WaatzeG
changed the title
|
@WaatzeG the title is confusing now. I guess you copied and pasted it. |
jeremylong
changed the title
|
Well, after careful review of this issue I am almost embarrassed to say what I did in my zealous upgrade of dependencies in the 3.1.0 release.... When I automated the dependency upgrade process I did not force the 3.1.0 maven api - instead, I allowed it to upgrade to 3.5.2 so ODC 3.1.0 will only work using Maven 3.5.2. This has been reverted to 3.1.0 and a release will be available shortly. |
|
I'm still seeing this messages with version 3.1.1 and Maven 3.3.9. Shouldn't it have been fixed? |
|
@jansohn I'm using version 3.1.1 with maven 3.3.9 without issue. |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I have two development machines. One contains maven 3.3.9, the other 3.5.2. Running
mvn verifyonly succeeds on maven version 3.5.2.Config in pom.xml:
Log output maven 3.3.9:
The text was updated successfully, but these errors were encountered: