[
http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154551#action_154551
]
James William Dumay commented on MRELEASE-326:
----------------------------------------------
This is because
{code}
@requiresDependencyResolution test
{code}
was annotated on the prepare mojo. Removing it makes the plugin happy - you
shouldn't try to force resolution for projects your about to build.
> Doens't resolve multiproject dependencies properly
> ---------------------------------------------------
>
> Key: MRELEASE-326
> URL: http://jira.codehaus.org/browse/MRELEASE-326
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7
> Environment: Windows, JDK 1.6, Maven 2.08
> Reporter: Kuno Baeriswyl
> Attachments: Stacktrace_release-plugin.txt
>
>
> I'd try to make a release:prepare from a multiproject:
> A (Multiproject POM)
> B (Core Interfaces)
> C (Component)
> D (Core Impl)
> E (Standalone Client)
> F (EJB)
> G (Client)
> A is the parent project and contains the other project from B to G. Following
> dependencies are defined : G -> F -> D -> B -> A
> However, when it comes to build the Artifact G, the release plugin aborts,
> because of missing Artifact F. But it's part of the Multiproject and was just
> build before. The release plugin checks the remote repository for an existing
> version. Which is non-sense, since I'm actually try to buld it right now...
> Since the release plugin has already changed the pom from Snapshot to stable
> version labels. I can now do "mvn install" and the missing Artefact will be
> installed. And the second run of mvn release:prepare will succeed! Though, I
> don't like this workaround and hope this can be fixed.
> Thanks
> Kuno
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
