o:[EMAIL PROTECTED]
> Sent: Thursday, March 09, 2006 10:08 PM
> To: Maven Users List
> Subject: Re: release:prepare errors
>
> On 3/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > The pom in the scm, I then check out the project then, I can run maven
>
> > fr
ubject: Re: release:prepare errors
On 3/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> The pom in the scm, I then check out the project then, I can run maven
> from the work directory.
>
> Then the release:prepare replaces the current pom with the tag pom
> that is gener
tagBase must be a real svn url and not a maven-scm url, it's the url to access to tags directory in
your svn
If you declare it in configuration of release plugin in your pom, you won't need to declare it on
command line
you don't need to declare the connection url to use, release plugin will
On 3/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> The pom in the scm, I then check out the project then, I can run maven from
> the work directory.
>
> Then the release:prepare replaces the current pom with the tag pom that is
> generated.
>
> Can someone help with this problem?
>
> Thanks
The pom in the scm, I then check out the project then, I can run maven from
the work directory.
Then the release:prepare replaces the current pom with the tag pom that is
generated.
Can someone help with this problem?
Thanks,
On 3/9/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
>
> It is, p
It is, poms should always be stored in your scm repository instead of
any proprietary IDE projects.
On 3/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I believe I am overwriting the pom tagBase with the command line for the
> tagBase!
>
> On 3/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wro
I believe I am overwriting the pom tagBase with the command line for the
tagBase!
On 3/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I can not get the *releases:prepare* command to work.
> I am using maven 2.0.2. Subversion 1.2.4.
> Also, it seems that the release:prepare is checkin the
I believe should be svn://css-paps/tmpSetup/projectName/tags
(without scm stuff)
Anyway, in your case you wouldn''t need to set it, since default is ../tags
On 3/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I can not get the *releases:prepare* command to work.
> I am using maven 2.0.2.
I can not get the *releases:prepare* command to work.
I am using maven 2.0.2. Subversion 1.2.4.
Also, it seems that the release:prepare is checkin the generated pom.xml to
my trunk. Is that suppose to happen?
I can do a command line for the svn copy.
mvn -e release:prepare -
Dproject.scm.develop
