-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency on Plexus Utils when using Maven Cache extension #472
Comments
This appears to possibly be a bug in the Maven Build Cache plugin. @debraj-manna since you found this initially... would it be possible to raise this on that project as well on their issue tracker? Happy to work with them to find the cause of this but I do not have experience using that extension. |
I have raised the below issue. |
Thanks! |
This comment was marked as off-topic.
This comment was marked as off-topic.
@zoujiaqing protocArtifact isn't an option in this plugin. Not sure this relates to this problem though? |
Sorry! |
Reported as https://issues.apache.org/jira/browse/MBUILDCACHE-115 IMHO this has nothing to do with plexus-utils. What made you think it is about plexus-utils? |
From the initial discussion at #470, seems that adding plexus-utils as a dependency resolves the issue in this case, or at the very least hides it. Thanks for raising the issue. |
Brief description
The use of the Maven Build Cache extension appears to force a dependency for this plugin on
plexus-utils
.This appears to be a bug with that extension, but this issue is raised to track any further developments.
Steps to reproduce
Run a build with the Maven Build Cache extension activated, and observe the plugin initialisation errors from the Protobuf Maven Plugin.
Error message
Logs
Operating system
macOS
JDK version
21
Maven version
3.9.9
Plugin version
2.7.0
Protoc version
3.24.0
Additional details
See #470 for the initial discussion.
See https://issues.apache.org/jira/browse/MBUILDCACHE-110 for the JIRA raised with Apache.
Would you like to contribute a bugfix?
The text was updated successfully, but these errors were encountered: