[
https://issues.apache.org/jira/browse/MPLUGIN-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461381#comment-17461381
]
Tamás Cservenák commented on MPLUGIN-385:
-----------------------------------------
Went thru Maven central exposed artifacts with group id "org.apache.maven":
most of them are obsolete, and there is maven core stuff and jxr and archiver.
In other words, if you use ANY of those that are not jxr, archiver or (current)
maven core stuff, something is really off with your project :D
Anyway, I plan to totally tune down this "warning": it will check ONLY for
maven-plugin-api (that is in provided scope), and if not, just warn you about
it, and rephrase the message to be less chatty (remove listing org.apache.maven
artifacts) and make it less aggressive (so remove "In the future this error
will break the build" and "Please fix your build!") and make it a one liner
with some message like "It is recommended to keep maven plugin api in provided
scope".
For your case [~kwin] it will work (as if you put maven-plugin-api into
provided, but maven-archiver in compile scopes, will not trigger).
WDYT?
> 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
> Priority: Major
>
> 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 starting with "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)
