[
https://issues.apache.org/jira/browse/MPLUGIN-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732691#comment-17732691
]
ASF GitHub Bot commented on MPLUGIN-473:
----------------------------------------
gnodet commented on PR #216:
URL:
https://github.com/apache/maven-plugin-tools/pull/216#issuecomment-1591807930
> I'm not sure if it is good way to resolve problems with plexus-utils and
maven-xml* artifacts. Currently we have a validators in Maven core which check
also transitive dependencies. So here verifications should be even more strict
than in Maven core. Maybe we can exclude maven-xml* artifacts?
>
> @cstamas what do you think?
That was a wrong idea. The plexus-xml is actually provided by maven 3 and 4
(at least the classes), so in most cases, the `plexus-xml` dependency itself
should be flagged as provided (contrary to the `plexus-utils` one).
> Better support for plexus-xml 4.x
> ---------------------------------
>
> Key: MPLUGIN-473
> URL: https://issues.apache.org/jira/browse/MPLUGIN-473
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Affects Versions: 3.9.0
> Reporter: Guillaume Nodet
> Priority: Major
>
> {code:java}
> [INFO] --- plugin:3.9.0:descriptor (mojo-descriptor) @ modello-maven-plugin
> ---
> [WARNING]
> Some dependencies of Maven Plugins are expected to be in provided scope.
> Please make sure that dependencies listed below declared in POM
> have set '<scope>provided</scope>' as well.
> The following dependencies are in wrong scope:
> * org.apache.maven:maven-xml-impl:jar:4.0.0-alpha-5:compile
> * org.apache.maven:maven-api-xml:jar:4.0.0-alpha-5:compile
> * org.apache.maven:maven-api-meta:jar:4.0.0-alpha-5:compile {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
