[jbosstools-issues] [JBoss JIRA] (JBIDE-16372) Can't build forge

Pavol Srna (JIRA) issues at jboss.org
Mon Feb 17 06:43:47 EST 2014


     [ https://issues.jboss.org/browse/JBIDE-16372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavol Srna closed JBIDE-16372.
------------------------------


    
> Can't build forge
> -----------------
>
>                 Key: JBIDE-16372
>                 URL: https://issues.jboss.org/browse/JBIDE-16372
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: forge
>            Reporter: Mickael Istria
>            Assignee: Koen Aers
>            Priority: Blocker
>             Fix For: 4.2.0.Alpha2
>
>
> When trying to build forge locally or on CI, we can see
> {quote}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.4:copy (get-runtime) on project org.jboss.tools.forge2.runtime: Unable to find artifact. Failure to find org.jboss.forge.addon:shell-api:jar:2.0.0.CR1 in http://repository.jboss.org/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced
> [ERROR] 
> [ERROR] Try downloading the file manually from the project website.
> [ERROR] 
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=org.jboss.forge.addon -DartifactId=shell-api -Dversion=2.0.0.CR1 -Dpackaging=jar -Dfile=/path/to/file
> [ERROR] 
> [ERROR] Alternatively, if you host your own repository you can deploy the file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.jboss.forge.addon -DartifactId=shell-api -Dversion=2.0.0.CR1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> [ERROR] 
> [ERROR] 
> [ERROR] org.jboss.forge.addon:shell-api:jar:2.0.0.CR1
> [ERROR] 
> [ERROR] from the specified remote repositories:
> [ERROR] jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=true),
> [ERROR] jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/, releases=true, snapshots=true),
> [ERROR] jboss-releases (https://repository.jboss.org/nexus/content/repositories/releases/, releases=true, snapshots=true),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false)
> [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/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR]   mvn <goals> -rf :org.jboss.tools.forge2.runtime
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list