Hi Johannes, Olivier! Took me some time to find a few free minutes but now I've coded the support for releasing child modules into maven-release-manager.
Please see MRELEASE-457 for a patch which needs to be reviewed before I'll check it in. LieGrue, strub ----- Original Message ---- > From: Johannes Schneider <[email protected]> > To: Maven Users List <[email protected]> > Sent: Fri, August 6, 2010 11:56:03 AM > Subject: Re: Releasing only one (sub)module within an SCM tree > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 08/06/2010 10:53 AM, Olivier Lamy wrote: > > Hi, > > Do you have a scm element in your module ? > > I tried it. At the moment I just have an scm element in my parent. > > > Just to be sure your tree is similar to : >http://github.com/olamy/scm-git-test ? > > And you want to release only my-app ? > > Yes, exactly. That is the scenario. Now I just want to remove the > modules section from the parent... > > > By the way it could be fixed if there was a way to do something like > > git clone [email protected]:olamy/scm-git-test.git/my-app > > Yes. But that is not possible... (Un)fortunately... > > Maven is build with Subversion in mind... Therefore the problems. > > > Johannes > > > > > Or doing some hackhish stuff for git in the release plugin. > > > > Can you load an issue on this ? (IHMO it looks to be reasonnable to > > add hack for such case) > > > > 2010/8/5 Johannes Schneider <[email protected]>: > > Hi, > > > > I have such a structure within my Git tree: > > > > daParent > > - moduleA > > - moduleB > > - ... > > > > Until today I released all modules together. This worked like a charm. > > > > Now I want to release the modules independently. But that does not work. > > > > I have removed the "modules" section from "daParent" and have been able > > to release that artifact successfully. > > Now I upgraded the parent version within moduleA and moduleB manually. > > > > But releasing moduleA does *not* work now. > > > > > > release:prepare works as expected, but release:perform checks out the > > the tagged version and tries to release "/pom.xml". > > Of course this pom is the pom of "daParent"... > > > > Since I am using Git I can't simply add a corrected scm tag to moduleA > > and moduleB... > > > > > > So how could I solve that? I experimented with > > -DpomFileName=moduleA/pom.xml but that did not work.... > > Any ideas are welcome... > > > > > > > > Thanks, > > > > Johannes > > > > > >> > - --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >> > >> > > - -- > Johannes Schneider - blog.cedarsoft.com > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQEcBAEBAgAGBQJMW9wwAAoJEAytD9R7Qv6dhWoH/j+KXnAlzOIwSqAXjQzvIrJn > B3VVp61ltm5kBLpl63aP0sIrWMde7QboSfcTjnsl5KA1NXvTm2XaybpNnmyJVXQs > YTI1J2h7/BoCIxeSzdN02mB6ptjZIkDwcAgjZkhUNTA41Q+3CoKE2lVwpYcjdTj8 > /gc0qj72Tfxw6SgzxVo5uWTxf7TPLxoXshFFAkj8xXtkpYEfUxvu0mlf/VZYVJp4 > ZWlBtD6u9kldNgfWtSEp3JJiLEeSi8PW3Ym8vQCVeAh5UAgzqtiTns5NPJEbE4vv > Tf46HLx55RY6nNI5XmbDr5xLzGMeIVbV3ehobsz9msZzqatmq9FIiTpFLut13b0= > =eAyX > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
