versioneye_maven_plugin icon indicating copy to clipboard operation
versioneye_maven_plugin copied to clipboard

mvn versioneye:create fails

Open rzvikas opened this issue 9 years ago • 4 comments

hi I keep getting following error when using versioneye:create command

Here is what I added to my pom.xml

<groupId>com.versioneye</groupId> <artifactId>versioneye-maven-plugin</artifactId> 3.11.0 <apiKey>xxxxx</apiKey>

[INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.924 s [INFO] Finished at: 2016-12-22T11:32:49-05:00 [INFO] Final Memory: 19M/304M [INFO] ------------------------------------------------------------------------ [ERROR] No plugin found for prefix 'versioneye' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (C:\Users\vikas_bali.m2\repository), calyps o-central-mirror (scp://cvs.calypso.com/home/releng/repo-thirdparty), codehaus-mojo-snapshots (http://snapshots.repository.codehaus.org/), codehaus-mojo-releases (http://repository.codehaus.org/), jboss-releases (https://repo sitory.jboss.org/nexus/content/groups/public/), central (https://repo.maven.apache.org/maven2)] -> [Help 1] [ERROR]

Thanks

rzvikas avatar Dec 22 '16 19:12 rzvikas

Hi @rzvikas It works for me and thousands of others, so it must be related to your setup. Which version of Java and Maven are you using? Are you behind a firewall? Behind a proxy? Can you provide a Vagrantfile or Docker Image with your setup?

reiz avatar Jan 04 '17 10:01 reiz

@rzvikas, I think the key part of the error message is: No plugin found for prefix 'versioneye' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo]

Maven is not looking for the plugin in the groupId com.versioneye, only in the two groupIds noted above, So, you have two options:

  • Instead of invoking mvn versioneye:create, invoke mvn com.versioneye:versioneye-maven-plugin:create
  • Add the groupId com.versioneye to //settings/pluginGroups in your Maven settings.xml

bindul avatar Jan 24 '17 21:01 bindul

The thing is that the README of the project explicitly states

Now you can check if the VersionEye API is available: mvn versioneye:ping

@bindul Thank you for the hint!

mvn com.versioneye:versioneye-maven-plugin:ping works fine.

koppor avatar Mar 17 '17 22:03 koppor

@rzvikas Is this still an issue? Or is this solved now?

reiz avatar May 25 '17 13:05 reiz