I guess you could make an aggregator pom in your trunk/ which kicks of all 3 builds. If you branch this pom it would succeed.
Or you could move your parent pom one level higher and let it serve as parent and aggregator pom. Hth, Nick Stolwijk ~Senior Java Developer~ iPROFS Wagenweg 208 2012 NM Haarlem T +31 23 547 6369 F +31 23 547 6370 I www.iprofs.nl 2011/6/20 Frédéric Conrotte <frederic.conro...@victorbuckservices.com>: > Hello > > Say you have a module named "parent" which has 2 childs "childA" and "ChildB" > > If I run > mvn release:branch -DbranchName=my-branch > in the "parent" folder, it will branch the parent module code to SVN > /branches/my-branch WITHOUT the 2 child modules. > > I would like release:branch to branch the parent module and all its children > to > . /branches/my-branch/parent > . /branches/my-branch/childA > . /branches/my-branch/childB > > I didn't found any solution in the doc yet: > . http://maven.apache.org/plugins/maven-release-plugin/branch-mojo.html > . http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html > > Is it feasible ? Or do I have to run the command for every module I want to > branch ? > > Any help would be appreciated, thanks > > Fred > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
