You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Christian Sauer <ch...@giniality.ch> on 2007/02/13 09:34:24 UTC
Maven, SCM and release builds
Hi all,
Is it possible to forbid the SCM plugin to generate the complete SCM connection in a
project's POM once a release build was performed?
Most of the SCM settings are specified as variables in the parent POM in order to allow
various developers performing release builds using alternating user ids for SCM
authentication. Currently the SCM section of a released projects' POM must be changed
manually by changing the user id in the connection string before performing a realease
build using an alternative user id.
any idea?
cheers,
chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven, SCM and release builds
Posted by Mark Struberg <st...@yahoo.de>.
Hi!
There is a workaround:
Specify a parent pom which holds the SCM information.
This way, the SCM info replacement will actually not
be part of your pom.
> <scm>
> <connection>
>
scm:cvs:pserver:${cvs.username}:${cvs.password}@cvs.intern:/home/cvsroot:${project.groupId}/
> </connection>
> <developerConnection..../>
> </scm>
We used the project.groupId as CVS module name to
unify the handling.
LieGrü,
strub
--- Christian Sauer <ch...@giniality.ch>
schrieb:
> Hi,
>
> thank you very much for the hint.
>
> cheers,
> chris
>
> -----Original Message-----
> From: "Tomasz Pik" <to...@gmail.com>
> To: "Maven Users List" <us...@maven.apache.org>
> Date: Tue, 13 Feb 2007 11:00:48 +0100
> Subject: Re: Maven, SCM and release builds
>
> > On 2/13/07, Christian Sauer
> <ch...@giniality.ch> wrote:
> > > Hi all,
> > >
> > > Is it possible to forbid the SCM plugin to
> generate the complete SCM connection in a
> > > project's POM once a release build was
> performed?
> > >
> > > Most of the SCM settings are specified as
> variables in the parent POM in order to
> > allow
> > > various developers performing release builds
> using alternating user ids for SCM
> > > authentication. Currently the SCM section of a
> released projects' POM must be changed
> > > manually by changing the user id in the
> connection string before performing a
> > realease
> > > build using an alternative user id.
> >
> > This has been already reported as an issue in
> JIRA, see
> > http://jira.codehaus.org/browse/MRELEASE-128.
> > So far I don't know a solution.
> >
> > Regards,
> > Tomek
> >
> >
>
---------------------------------------------------------------------
> > 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
>
>
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven, SCM and release builds
Posted by Christian Sauer <ch...@giniality.ch>.
Hi,
thank you very much for the hint.
cheers,
chris
-----Original Message-----
From: "Tomasz Pik" <to...@gmail.com>
To: "Maven Users List" <us...@maven.apache.org>
Date: Tue, 13 Feb 2007 11:00:48 +0100
Subject: Re: Maven, SCM and release builds
> On 2/13/07, Christian Sauer <ch...@giniality.ch> wrote:
> > Hi all,
> >
> > Is it possible to forbid the SCM plugin to generate the complete SCM connection in a
> > project's POM once a release build was performed?
> >
> > Most of the SCM settings are specified as variables in the parent POM in order to
> allow
> > various developers performing release builds using alternating user ids for SCM
> > authentication. Currently the SCM section of a released projects' POM must be changed
> > manually by changing the user id in the connection string before performing a
> realease
> > build using an alternative user id.
>
> This has been already reported as an issue in JIRA, see
> http://jira.codehaus.org/browse/MRELEASE-128.
> So far I don't know a solution.
>
> Regards,
> Tomek
>
> ---------------------------------------------------------------------
> 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: Maven, SCM and release builds
Posted by Tomasz Pik <to...@gmail.com>.
On 2/13/07, Christian Sauer <ch...@giniality.ch> wrote:
> Hi all,
>
> Is it possible to forbid the SCM plugin to generate the complete SCM connection in a
> project's POM once a release build was performed?
>
> Most of the SCM settings are specified as variables in the parent POM in order to allow
> various developers performing release builds using alternating user ids for SCM
> authentication. Currently the SCM section of a released projects' POM must be changed
> manually by changing the user id in the connection string before performing a realease
> build using an alternative user id.
This has been already reported as an issue in JIRA, see
http://jira.codehaus.org/browse/MRELEASE-128.
So far I don't know a solution.
Regards,
Tomek
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org