You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Evgeny Goldin <ev...@gmail.com> on 2011/01/30 17:27:10 UTC
Supporting branches in Maven
Hi everybody,
We have a number of branches built with Maven. If we do nothing then
artifacts from different branches will override each other in local maven
repo and corporate repo manager. So we have a Groovy script that modifies
<groupId> or <version> of all POMs in a branch, by adding a branch name to
it.
I suppose maven release plugin can also do that but we haven't tried it yet.
My question is how other people solve this issue of building different
branches and storing artifacts in the same repo (be it local or remote)?
-----
Best regards,
Evgeny
http://evgeny-goldin.com/ evgeny-goldin.com
--
View this message in context: http://maven.40175.n5.nabble.com/Supporting-branches-in-Maven-tp3363522p3363522.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Supporting branches in Maven
Posted by Arnaud Héritier <ar...@exoplatform.com>.
We are also only using a change in the version.
We often use the release:branch mojo to create the branch but sometimes we
do it manually with versions:set to update all versions.
Arnaud
On Sun, Jan 30, 2011 at 10:42 PM, Evgeny Goldin <ev...@gmail.com> wrote:
>
> Thanks, I see "release:branch" is the common way so it means we're doing
> basically the same.
>
> -----
> Best regards,
>
> Evgeny
>
> http://evgeny-goldin.com/ evgeny-goldin.com
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Supporting-branches-in-Maven-tp3363522p3363783.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Supporting branches in Maven
Posted by Evgeny Goldin <ev...@gmail.com>.
Thanks, I see "release:branch" is the common way so it means we're doing
basically the same.
-----
Best regards,
Evgeny
http://evgeny-goldin.com/ evgeny-goldin.com
--
View this message in context: http://maven.40175.n5.nabble.com/Supporting-branches-in-Maven-tp3363522p3363783.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Supporting branches in Maven
Posted by Justin Edelson <ju...@justinedelson.com>.
Different branches = different versions. Read the list archives for more
information.
Justin
On Sun, Jan 30, 2011 at 11:27 AM, Evgeny Goldin <ev...@gmail.com> wrote:
>
> Hi everybody,
>
> We have a number of branches built with Maven. If we do nothing then
> artifacts from different branches will override each other in local maven
> repo and corporate repo manager. So we have a Groovy script that modifies
> <groupId> or <version> of all POMs in a branch, by adding a branch name to
> it.
>
> I suppose maven release plugin can also do that but we haven't tried it
> yet.
> My question is how other people solve this issue of building different
> branches and storing artifacts in the same repo (be it local or remote)?
>
>
> -----
> Best regards,
>
> Evgeny
>
> http://evgeny-goldin.com/ evgeny-goldin.com
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Supporting-branches-in-Maven-tp3363522p3363522.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>