Skip to content
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

mvn versioneye:create fails #72

Open
rzvikas opened this issue Dec 22, 2016 · 4 comments
Open

mvn versioneye:create fails #72

rzvikas opened this issue Dec 22, 2016 · 4 comments

Comments

@rzvikas
Copy link

rzvikas commented Dec 22, 2016

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

Here is what I added to my pom.xml

com.versioneye versioneye-maven-plugin 3.11.0 xxxxx

[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

@reiz
Copy link
Member

reiz commented Jan 4, 2017

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?

@bindul
Copy link

bindul commented Jan 24, 2017

@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

@koppor
Copy link

koppor commented Mar 17, 2017

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.

@reiz
Copy link
Member

reiz commented May 25, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants