[jira] Commented: (MRELEASE-326) Doens't resolve multiproject dependencies properly
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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] Commented: (MRELEASE-326) Doens't resolve multiproject dependencies properly
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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] Created: (MCHECKSTYLE-73) Checkstyle has trouble locating config file using build extensions in a multi-module project
Checkstyle has trouble locating config file using build extensions in a multi-module project Key: MCHECKSTYLE-73 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-73 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.1 Environment: Windows 2000 Workstation / Windows Server 2003 Reporter: Ian Rowlands Priority: Minor The example used to configure a multi-module project fails to work when you add additional java code to the project containing the config file. To reproduce: 1. Create 2 projects (call them A and Z). A is the parent of Z. Z contains the code, and is where you run the site command from. 2. Create another project (called Build). This contains the checkstyle config file. 3. Configure project A to use Build as an extension (as specified in http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html). 4. Run mvn site in project Z, after deploying the other projects. 5. Add some java code to project Build, and deploy it. 6. Run mvn site in project Z, which produces the following error: Embedded error: Error rendering Maven report: Unable to find configuration file location. As soon as you take out the java code, everything goes back to normal. There is a workaround - set project Build as a plugin dependency. This has no problems in both cases. -- 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
