You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Johannes Schneider <ma...@cedarsoft.com> on 2010/08/05 22:30:00 UTC
Releasing only one (sub)module within an SCM tree
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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
- --
Johannes Schneider - blog.cedarsoft.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJMWx9FAAoJEAytD9R7Qv6dfCYIAMPeb9WfTX4hntgj6CnNwXUw
8/CnY2KgSBadoPDGW4zSF+XS2/RyosU9gmmBYyNyqfKm/fMoI/DrXp3KOG4SZ7a7
owX3QMBRPRPqOGXT8z9kp9rOVYY5HodZXHmbU7GKuMpNFgYz9zIPpscFWS+1ohhT
2szO2OMPfPsSBgq3Py6rchQXZigMD+dLB2lTrjdZ9jApo1b4ZlrnQDAZEnWCHhki
E5tVBTRyCRMwTEDFdsdr0lX9LLX9gn/8ViOTayS5gnd/PxaftRRfSrmKltPDwygw
GbrmgQGtXi+/OnOX2tRfllYUqsoPrANzMEFvE5mTq44p45Q75bNZ8dtbm3+KgdY=
=/OF4
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Releasing only one (sub)module within an SCM tree
Posted by Mark Struberg <st...@yahoo.de>.
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 <ma...@cedarsoft.com>
> To: Maven Users List <us...@maven.apache.org>
> 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 git@github.com: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 <ma...@cedarsoft.com>:
> > 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
>
> - --
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Releasing only one (sub)module within an SCM tree
Posted by Johannes Schneider <ma...@cedarsoft.com>.
-----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 git@github.com: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 <ma...@cedarsoft.com>:
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
>>
>>
- --
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Releasing only one (sub)module within an SCM tree
Posted by Olivier Lamy <ol...@apache.org>.
Hi,
Do you have a scm element in your module ?
Just to be sure your tree is similar to : http://github.com/olamy/scm-git-test ?
And you want to release only my-app ?
By the way it could be fixed if there was a way to do something like
git clone git@github.com:olamy/scm-git-test.git/my-app
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 <ma...@cedarsoft.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 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
>
>
> - --
> Johannes Schneider - blog.cedarsoft.com
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQEcBAEBAgAGBQJMWx9FAAoJEAytD9R7Qv6dfCYIAMPeb9WfTX4hntgj6CnNwXUw
> 8/CnY2KgSBadoPDGW4zSF+XS2/RyosU9gmmBYyNyqfKm/fMoI/DrXp3KOG4SZ7a7
> owX3QMBRPRPqOGXT8z9kp9rOVYY5HodZXHmbU7GKuMpNFgYz9zIPpscFWS+1ohhT
> 2szO2OMPfPsSBgq3Py6rchQXZigMD+dLB2lTrjdZ9jApo1b4ZlrnQDAZEnWCHhki
> E5tVBTRyCRMwTEDFdsdr0lX9LLX9gn/8ViOTayS5gnd/PxaftRRfSrmKltPDwygw
> GbrmgQGtXi+/OnOX2tRfllYUqsoPrANzMEFvE5mTq44p45Q75bNZ8dtbm3+KgdY=
> =/OF4
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Olivier
http://twitter.com/olamy
http://fr.linkedin.com/in/olamy
http://www.viadeo.com/fr/profile/olivier.lamy7
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org