[
https://issues.apache.org/jira/browse/MSHARED-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197180#comment-17197180
]
Henning Schmiedehausen commented on MSHARED-957:
------------------------------------------------
Thank you for looking into this. I mainly raised this because it confused me
that a simple "last digit version change" completely broke the plugin. I
understand that there is no obligation or requirement to follow and specific
release versioning guidelines in a specific Apache project.
I am not sure what the point of using three digit versioning is if it is not
using semantic versioning. If "x.x.0" and "x.x.1" exhibit the same possible
differences than "1.x.x" and "2.x.x", then why not just call the releases "1",
"2", "3" and not give any guarantees at all.
My assumption always was that any Apache release that uses three digit
versioning, also uses semantic (or its predecessors as Apache predates semantic
versioning). The grand daddy of all apache project versioning schemes (the APR
project) seems to imply this: https://apr.apache.org/versioning.html
I understand that other Apache projects may use different versioning schemes,
but it is hard for me to see the point, if the different digits are simply
incremented at random.
I will be sticking with 1.11.1 for now; looking forward to see a new release of
the dependency plugin.
> API incompatibility between versions 1.11.1 and 1.11.2
> ------------------------------------------------------
>
> Key: MSHARED-957
> URL: https://issues.apache.org/jira/browse/MSHARED-957
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-analyzer
> Environment: mvn --version
> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
> Maven home: /home/henning/.local/share/apache-maven-3.6.3
> Java version: 11.0.8, vendor: Red Hat, Inc., runtime:
> /usr/lib/jvm/java-11-openjdk-11.0.8.10-2.fc32.x86_64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.8.4-200.fc32.x86_64", arch: "amd64", family:
> "unix"
> Reporter: Henning Schmiedehausen
> Assignee: Elliotte Rusty Harold
> Priority: Major
>
> Using the dependency analyzer as an explicit dependency for the dependency
> plugin:
>
> {quote}<plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-dependency-plugin</artifactId>
> <version>3.1.12</version>
> <dependencies>
> <dependency>
> <groupId>org.apache.maven.shared</groupId>
> <artifactId>maven-dependency-analyzer</artifactId>
> <version>1.11.1</version>
> </dependency>
> </dependencies>
> ...
> {quote}
> This works fine with version 1.11.1. Upgrading to 1.11.2 (or 1.11.3), which
> are supposed (at least that is implied by the semantic versioning) fully
> compatible to 1.11.1 yields
> {{ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only (default)
> on project duplicate-finder-maven-plugin: Execution default of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.1.2:analyze-only failed:
> Unsupported api 524288 -> [Help 1]}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
