[ http://jira.codehaus.org/browse/MNG-1053?page=comments#action_47672 ]
Mark Hobson commented on MNG-1053: ---------------------------------- Sorry it may have been a bit cryptic ;) I was referring to the "major versions are incompatible" bit, which I would have thought implied that the reactor should abide by the same rules & build both 1.x and 2.x. Is there any reason why the reactor must only build one version of a project? I have a few projects where 1.x and 2.x development occurs simultaneously in the same scm with the same group & artifact ids. It seems a bit daft having to add a '2' suffix to the 2.x artifact id so that the reactor picks it up - you end up artifactId2-2.0.jar :) > Reactor mediates projects like dependencies > ------------------------------------------- > > Key: MNG-1053 > URL: http://jira.codehaus.org/browse/MNG-1053 > Project: Maven 2 > Type: Bug > Components: maven-core > Versions: 2.0-beta-3 > Environment: Windows XP, Cygwin > Reporter: Mark Hobson > Assignee: Brett Porter > Attachments: test.zip > > > The attached zip contains the following projects: > test:a:1.0 > test:a:2.0 > Running m2 -r install in the project's parent directory results in only > test:a:2.0 being built. It appears that m2 mediates out projects in the > reactor in the same manner as dependencies. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
