[
http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162814#action_162814
]
Thiago Leão Moreira commented on MRELEASE-326:
----------------------------------------------
This problem occurs when one project produces more than one artifact that will
be used on other projects. Like this:
Project Foo produces Foo-1.0.jar and Foo-1.0-test.jar artifacts.
Project Bar depends on Foo-1.0.jar and Foo1.0-test.jar artifacts. The former
artifact is resolved without problem but the latter is not since it isn't the
main artifact produced by the Foo project.
The sample provided by Kuno show this perfectly: Project F produces two
artifcats (EJB-jar and client-jar) and project G dependes on the client-jar of
F (which is a second jar produced by F).
> 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
> Components: prepare
> Affects Versions: 2.0-beta-7
> Environment: Windows, JDK 1.6, Maven 2.08
> Reporter: Kuno Baeriswyl
> Fix For: 2.0-beta-9
>
> 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
