You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "gnodet (via GitHub)" <gi...@apache.org> on 2023/05/23 08:43:48 UTC
[GitHub] [maven-plugin-tools] gnodet opened a new pull request, #216: [MPLUGIN-473] Only check direct dependencies for provided scope
gnodet opened a new pull request, #216:
URL: https://github.com/apache/maven-plugin-tools/pull/216
This relaxes the check a bit and provides support for plexus-xml 4.0.0
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-plugin-tools] slawekjaranowski commented on pull request #216: [MPLUGIN-473] Only check direct dependencies for provided scope
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on PR #216:
URL: https://github.com/apache/maven-plugin-tools/pull/216#issuecomment-1560057191
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?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-plugin-tools] gnodet commented on pull request #216: [MPLUGIN-473] Only check direct dependencies for provided scope
Posted by "gnodet (via GitHub)" <gi...@apache.org>.
gnodet commented on PR #216:
URL: https://github.com/apache/maven-plugin-tools/pull/216#issuecomment-1558832031
This should provide a fix for https://github.com/codehaus-plexus/plexus-utils/issues/256 and https://github.com/codehaus-plexus/plexus-xml/issues/16
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-plugin-tools] gnodet commented on pull request #216: [MPLUGIN-473] Only check direct dependencies for provided scope
Posted by "gnodet (via GitHub)" <gi...@apache.org>.
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).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-plugin-tools] gnodet closed pull request #216: [MPLUGIN-473] Only check direct dependencies for provided scope
Posted by "gnodet (via GitHub)" <gi...@apache.org>.
gnodet closed pull request #216: [MPLUGIN-473] Only check direct dependencies for provided scope
URL: https://github.com/apache/maven-plugin-tools/pull/216
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org