[MRELEASE-326] Doens't resolve multiproject dependencies properly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0-beta-7
• Component/s: prepare
• Environment: Windows, JDK 1.6, Maven 2.08
• Assignee: Olivier Lamy
• Reporter: Kuno Baeriswyl
• Created: 29/Feb/08 03:08
• Updated: 19/Mar/09 17:17
• Resolved: 19/Mar/09 17:17

Description

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

Issue Links

• is related to: MRELEASE-388 @requiresDependencyResolution on prepare mojo causes build to look for its own dependencies
• is related to: MNG-2871 Subartifact (ejb-client, test-jar etc.) are not reselved as active project artifacts in build phases prior to package
• is related to: MNG-3043 Allow 'mvn test' to work with test-jar dependencies in a reactor
• is related to: MRELEASE-3 release:prepare should not require multimodule artifacts to be in the local repository