i have an application project that owns one child module, but both live in different locations in cvs. the app is atree/App whild the child is ctree/Module, so right away we can see we're dealing with "the hierarchy is flat" thinking. the flat heirarchy is inescapable at this time, and really provides a nice logical separation anyway, so the goal is to preserve it.
in order to facilitate using scm:checkout after atree/App is checked out using a cvs client or commandline, i created a checkout.pom which contains the scmurl to the ctree/Module and thus checks it out into atree/App. after that, the usual atree/App/pom.xml can do most everything with atree/App/Module that it needs to...except release:perform. release:prepare succeeds in creating a release.properties file that contains the following significant lines: scm.url=scm\:cvs\:pserver\:username\:@mycvs\:/cvs\:atree/App project.scm.atree\:App.connection=scm\:cvs\:pserver\:username\:@mycvs\:/cvs\:atree/App project.scm.ctree\:Module.connection=scm\:cvs\:pserver\:username\:@mycvs\:/cvs\:ctree/Module obviously, when release:perform does its checkout into target/checkout, it uses the scm.url thereby missing out on the child module code altogether, so the remainder of release:perform fails when it can't find an atree/App/Module/pom.xml to work with. but what about those project.scm urls? why doesn't the release plugin use those when it retrieves the App and Module? both of those values come from the respective scm sections in the pom.xmls and are where the code actually lives...couldn't the release plugin realize which is the parent project's scm url, check it out as target/checkout, and then check out all the child projects into target/checkout (with all checkouts done using the release tag)? this is killing me...i've tried all manner of plugin configs and executions to coerce maven into checking out the child modules with no success. worse, i've realized that even if i had gotten any of my child checkout attempts to succeed, it wouldn't have been the correct, tagged version, it would have been the HEAD. i tried using maven-release-plugin-2.0.5-SNAPSHOT, but that version is from June and didn't solve anything. has anyone else had any success in doing multi-module releases with flat modules? thanks, jdc -- View this message in context: http://www.nabble.com/releases-on-multi-module-project-with-different-scm-urls-tf2776836s177.html#a7746955 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
