versions: Failed to execute goal `org.codehaus.mojo:versions-maven-plugin:2.14.1:set`

Hiho, guys, can you help with the next issue?

[ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:2.14.1:set (default-cli) on project oapi-bulk-operations: Execution default-cli of goal org.codehaus.mojo:versions-maven-plugin:2.14.1:set failed: Unable to load the mojo 'set' (or one of its required components) from the plugin 'org.codehaus.mojo:versions-maven-plugin:2.14.1': com.google.inject.ProvisionException: Guice provision errors:
   [ERROR]
   [ERROR] 1) Could not find a suitable constructor in org.codehaus.mojo.versions.SetMojo. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private.
   [ERROR] at org.codehaus.mojo.versions.SetMojo.class(Unknown Source)
   [ERROR] while locating org.codehaus.mojo.versions.SetMojo
   [ERROR] at ClassRealm[plugin>org.codehaus.mojo:versions-maven-plugin:2.14.1, parent: sun.misc.Launcher$AppClassLoader@7852e922]
   [ERROR] while locating org.apache.maven.plugin.Mojo annotated with @com.google.inject.name.Named(value=org.codehaus.mojo:versions-maven-plugin:2.14.1:set)
   [ERROR]
   [ERROR] 1 error
   [ERROR] role: org.apache.maven.plugin.Mojo
   [ERROR] roleHint: org.codehaus.mojo:versions-maven-plugin:2.14.1:set
   [ERROR] -> [Help 1]
   [ERROR]
   [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
   [ERROR] Re-run Maven using the -X switch to enable full debug logging.
   [ERROR]
   [ERROR] For more information about the errors and possible solutions, please read the following articles:
   [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
   Process exited with code 1

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 15 (8 by maintainers)

Most upvoted comments

@slawekjaranowski should this be closed? Looks like attempts to execute the plugin with an unsupported Maven version.

That is an excellent question. As I was looking through the debug logs, I saw that our jenkins build was using 3.0.5, there is some misconfiguration on our end. I was able to reproduce it on my laptop by setting the version to 3.0.5. Clearly the solution is to update to the higher maven version like 3.5.0

Thank you!