You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kuno Baeriswyl (JIRA)" <ji...@codehaus.org> on 2008/02/29 10:09:28 UTC
[jira] Created: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
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
[jira] Commented: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139028#action_139028 ]
Paul Gier commented on MRELEASE-326:
------------------------------------
Anyone have a sample project that they can upload that reproduces this?
> 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
[jira] Updated: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James William Dumay updated MRELEASE-326:
-----------------------------------------
Comment: was deleted
> 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
[jira] Issue Comment Edited: (MRELEASE-326) Doens't resolve
multiproject dependencies properly
Posted by "Luc Willems (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151824#action_151824 ]
luc.willems edited comment on MRELEASE-326 at 10/24/08 9:05 AM:
----------------------------------------------------------------
doesn't work for me :-(
dependency errors are thrown before any clean/install goal has been run.
using maven 2.0.9 and maven-release-plugin version 2.0-beta-7
was (Author: luc.willems):
doesn't work for me :-(
dependency errors are thrown before any clean/install goal has been run.
> 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
[jira] Commented: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
Posted by "Ian Rowlands (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138702#action_138702 ]
Ian Rowlands commented on MRELEASE-326:
---------------------------------------
Is this being worked on? No progress seems to have been made.
> 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
[jira] Updated: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-326:
-------------------------------------
Fix Version/s: 2.0-beta-9
> 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
> 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
[jira] Closed: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed MRELEASE-326.
---------------------------------
Assignee: Olivier Lamy
Resolution: Duplicate
Fix Version/s: (was: 2.0-beta-9)
duplicate with MRELEASE-3
> 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
> Assignee: Olivier Lamy
> 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
[jira] Commented: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
Posted by "Thiago Leão Moreira (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
Posted by "Ian Rowlands (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133499#action_133499 ]
Ian Rowlands commented on MRELEASE-326:
---------------------------------------
Still a problem with 2.0.8 - this means unless you have the dependencies done in a certain way, releases cannot be automated.
> 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
[jira] Updated: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James William Dumay updated MRELEASE-326:
-----------------------------------------
Attachment: MRELEASE-326.patch
Adding patch that removes the @requiresDependencyResolution doclet
> 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
[jira] Updated: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
Posted by "James William Dumay (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James William Dumay updated MRELEASE-326:
-----------------------------------------
Attachment: (was: MRELEASE-326.patch)
> 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
[jira] Updated: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-326:
-------------------------------------
Component/s: prepare
> 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
[jira] Commented: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
Posted by "Kalle Korhonen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139211#action_139211 ]
Kalle Korhonen commented on MRELEASE-326:
-----------------------------------------
This is the documented behavior of the release plugin right? By default, release:prepare doesn't run install goal. If you need it, you can configure it to run "clean install" as instructed at http://maven.apache.org/plugins/maven-release-plugin/examples/run-goals-before-commit.html
> 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
[jira] Commented: (MRELEASE-326) Doens't resolve multiproject
dependencies properly
Posted by "Luc Willems (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151824#action_151824 ]
Luc Willems commented on MRELEASE-326:
--------------------------------------
doesn't work for me :-(
dependency errors are thrown before any clean/install goal has been run.
> 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