You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/12/16 16:14:00 UTC

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

Konrad Windszus created MPLUGIN-385:
---------------------------------------

             Summary: Clarify usage of scope "provided" for Maven artifacts with group id "org.apache.maven"
                 Key: MPLUGIN-385
                 URL: https://issues.apache.org/jira/browse/MPLUGIN-385
             Project: Maven Plugin Tools
          Issue Type: Improvement
          Components: Plugin Plugin
    Affects Versions: 3.6.2
            Reporter: Konrad Windszus


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
{code}
java.lang.NoClassDefFoundError: Lorg/apache/maven/archiver/MavenArchiveConfiguration;
{code}

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 below "org.apache.maven" like "org.apache.maven.shared"?

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



--
This message was sent by Atlassian Jira
(v8.20.1#820001)