maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James William Dumay (JIRA)" <>
Subject [jira] Updated: (MRELEASE-326) Doens't resolve multiproject dependencies properly
Date Tue, 18 Nov 2008 05:59:42 GMT


James William Dumay updated MRELEASE-326:

    Attachment:     (was: MRELEASE-326.patch)

> Doens't resolve  multiproject dependencies properly
> ---------------------------------------------------
>                 Key: MRELEASE-326
>                 URL:
>             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:
For more information on JIRA, see:


View raw message