[MPLUGIN-385] Clarify usage of scope "provided" for Maven artifacts with group id "org.apache.maven"

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.6.2
• Component/s: Plugin Plugin
• Assignee: Unassigned
• Reporter: Konrad Windszus
• Created: 16/Dec/21 16:13
• Updated: 29/Nov/22 17:46

Description

Since m-plugin-p 3.6.2 (MPLUGIN-370) all dependencies with group id org.apache.maven are supposed to be referenced with scope provided.
But once turning dependency org.apache.maven:maven-archiver:3.5.1 to scope provided my ITs based on org.apache.maven.shared:maven-verifier:1.7.2 are starting to fail with NCDF errors

java.lang.NoClassDefFoundError: Lorg/apache/maven/archiver/MavenArchiveConfiguration;

Is that a bug in the classloader with maven-verifier? What if I want to use a newer version than shipped with Maven like "maven-archiver 3.5.1"?
What about group ids starting with "org.apache.maven" like "org.apache.maven.shared"?

You can reproduce with https://github.com/apache/jackrabbit-filevault-package-maven-plugin.

Issue Links

• relates to: MPLUGIN-370 check that plugin dependencies that are already exported by Maven are scope provided
• relates to: MPLUGIN-386 Filter out maven-archiver and maven-jxr from scope warning
• links to: GitHub Pull Request #56