You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marius Dumitru Florea (JIRA)" <ji...@codehaus.org> on 2012/02/16 16:55:03 UTC
[jira] (MRELEASE-730) release:prepare cannot find dependent
artefact
[ https://jira.codehaus.org/browse/MRELEASE-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291936#comment-291936 ]
Marius Dumitru Florea commented on MRELEASE-730:
------------------------------------------------
I had a similar problem while using Maven 3.0.3. Upgrading to 3.0.4 fixed the problem for me.
> release:prepare cannot find dependent artefact
> ----------------------------------------------
>
> Key: MRELEASE-730
> URL: https://jira.codehaus.org/browse/MRELEASE-730
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.2.2
> Reporter: Thomas Diesler
>
> It seems that release:prepare assumes dependencies to come from central
> {code}
> [tdiesler@tdvaio jbosgi-resolver]$ mvn release:prepare
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] JBossOSGi Resolver
> [INFO] JBossOSGi Resolver API
> [INFO] JBossOSGi Resolver Felix
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBossOSGi Resolver 2.0.0.Alpha5-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ jbosgi-resolver-parent ---
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: pom.xml.next, release.properties, pom.xml.releaseBackup, pom.xml.backup, pom.xml.branch, pom.xml.tag
> [INFO] Executing: /bin/sh -c cd /home/tdiesler/git/jbosgi-resolver && git status
> [INFO] Working directory: /home/tdiesler/git/jbosgi-resolver
> [INFO] Checking dependencies and plugins for snapshots ...
> What is the release version for "JBossOSGi Resolver"? (org.jboss.osgi.resolver:jbosgi-resolver-parent) 2.0.0.Alpha5: :
> What is the release version for "JBossOSGi Resolver API"? (org.jboss.osgi.resolver:jbosgi-resolver-apiv2) 2.0.0.Alpha5: :
> What is the release version for "JBossOSGi Resolver Felix"? (org.jboss.osgi.resolver:jbosgi-resolver-felix) 2.0.0.Alpha5: :
> What is SCM release tag or label for "JBossOSGi Resolver"? (org.jboss.osgi.resolver:jbosgi-resolver-parent) jbosgi-resolver-parent-2.0.0.Alpha5: :
> What is the new development version for "JBossOSGi Resolver"? (org.jboss.osgi.resolver:jbosgi-resolver-parent) 2.0.1.Alpha5-SNAPSHOT: :
> What is the new development version for "JBossOSGi Resolver API"? (org.jboss.osgi.resolver:jbosgi-resolver-apiv2) 2.0.1.Alpha5-SNAPSHOT: :
> What is the new development version for "JBossOSGi Resolver Felix"? (org.jboss.osgi.resolver:jbosgi-resolver-felix) 2.0.1.Alpha5-SNAPSHOT: :
> [INFO] Transforming 'JBossOSGi Resolver'...
> [INFO] Transforming 'JBossOSGi Resolver API'...
> [INFO] Transforming 'JBossOSGi Resolver Felix'...
> [INFO] Ignoring artifact version update for expression ${project.version}
> [INFO] Not generating release POMs
> [INFO] Executing goals 'clean verify'...
> [WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance.
> [INFO] [INFO] Scanning for projects...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Build Order:
> [INFO] [INFO]
> [INFO] [INFO] JBossOSGi Resolver
> [INFO] [INFO] JBossOSGi Resolver API
> [INFO] [INFO] JBossOSGi Resolver Felix
> [INFO] [INFO]
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Building JBossOSGi Resolver 2.0.0.Alpha5
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO]
> [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ jbosgi-resolver-parent ---
> [INFO] [INFO] Deleting /home/tdiesler/git/jbosgi-resolver/target
> [INFO] [INFO]
> [INFO] [INFO] >>> maven-source-plugin:2.1.2:jar (attach-sources) @ jbosgi-resolver-parent >>>
> [INFO] [INFO]
> [INFO] [INFO] <<< maven-source-plugin:2.1.2:jar (attach-sources) @ jbosgi-resolver-parent <<<
> [INFO] [INFO]
> [INFO] [INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @ jbosgi-resolver-parent ---
> [INFO] [INFO]
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Building JBossOSGi Resolver API 2.0.0.Alpha5
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] Downloading: http://repo1.maven.org/maven2/org/jboss/osgi/vfs/jbosgi-vfs30/1.0.6/jbosgi-vfs30-1.0.6.pom
> [INFO]
> [INFO] [WARNING] The POM for org.jboss.osgi.vfs:jbosgi-vfs30:jar:1.0.6 is missing, no dependency information available
> [INFO] Downloading: http://repo1.maven.org/maven2/org/jboss/osgi/vfs/jbosgi-vfs30/1.0.6/jbosgi-vfs30-1.0.6.jar
> [INFO]
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Reactor Summary:
> [INFO] [INFO]
> [INFO] [INFO] JBossOSGi Resolver ................................ SUCCESS [1.276s]
> [INFO] [INFO] JBossOSGi Resolver API ............................ FAILURE [0.743s]
> [INFO] [INFO] JBossOSGi Resolver Felix .......................... SKIPPED
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Total time: 2.728s
> [INFO] [INFO] Finished at: Tue Jan 24 11:47:20 CET 2012
> [INFO] [INFO] Final Memory: 4M/71M
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [WARNING] The requested profile "default" could not be activated because it does not exist.
> [INFO] [ERROR] Failed to execute goal on project jbosgi-resolver-apiv2: Could not resolve dependencies for project org.jboss.osgi.resolver:jbosgi-resolver-apiv2:jar:2.0.0.Alpha5: Could not find artifact org.jboss.osgi.vfs:jbosgi-vfs30:jar:1.0.6 in central (http://repo1.maven.org/maven2) -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [INFO] [ERROR]
> [INFO] [ERROR] After correcting the problems, you can resume the build with the command
> [INFO] [ERROR] mvn <goals> -rf :jbosgi-resolver-apiv2
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBossOSGi Resolver ................................ FAILURE [14.247s]
> [INFO] JBossOSGi Resolver API ............................ SKIPPED
> [INFO] JBossOSGi Resolver Felix .......................... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 15.193s
> [INFO] Finished at: Tue Jan 24 11:47:20 CET 2012
> [INFO] Final Memory: 6M/103M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) on project jbosgi-resolver-parent: Maven execution failed, exit code: '1' -> [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
> {code}
> This works with 2.2.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira