You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Barrie Treloar <ba...@gmail.com> on 2009/03/23 12:44:18 UTC
Re-Releasing plugin steps.
http://maven.apache.org/developers/release/releasing.html
Step 6. Verify the Staged artifacts
Indicates that if I dont like the contents I can drop the repository
and rollback the release.
If I then try release:prepare again I get a failure:
[INFO] Working directory: D:\ide\maven\maven-eclipse-plugin
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Path 'https://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-2.6'
already exists
What's the correct way of re-releaing a plugin that either was stuffed
up before a vote or fails the vote?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Re-Releasing plugin steps.
Posted by Olivier Lamy <ol...@apache.org>.
2009/3/23 Jason van Zyl <jv...@sonatype.com>:
> I can just release it with the current version no?
No the fix for svn 1.5.0+ requires a scm 1.2 !
>
> When are you going to release scm?
Tonigth (note : I'm on GMT timezone :-) ) .
>
> On 23-Mar-09, at 9:00 AM, Olivier Lamy wrote:
>
>> this need a maven-scm release before.
>> It's on my todo list.
>>
>> --
>> Olivier
>>
>> 2009/3/23 Jason van Zyl <jv...@sonatype.com>:
>>>
>>> I'm going to stage the release plugin tonight.
>>>
>>> On 23-Mar-09, at 6:07 AM, Olivier Lamy wrote:
>>>
>>>> Hi,
>>>> A very famous issue ! http://jira.codehaus.org/browse/MRELEASE-375
>>>>
>>>> My next days jobs will be releasing maven-scm and release-plugin :-))
>>>>
>>>> --
>>>> Olivier
>>>>
>>>> 2009/3/23 Barrie Treloar <ba...@gmail.com>:
>>>>>
>>>>> http://maven.apache.org/developers/release/releasing.html
>>>>>
>>>>> Step 6. Verify the Staged artifacts
>>>>>
>>>>> Indicates that if I dont like the contents I can drop the repository
>>>>> and rollback the release.
>>>>>
>>>>> If I then try release:prepare again I get a failure:
>>>>>
>>>>> [INFO] Working directory: D:\ide\maven\maven-eclipse-plugin
>>>>> [INFO]
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>> [ERROR] BUILD FAILURE
>>>>> [INFO]
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] Unable to tag SCM
>>>>> Provider message:
>>>>> The svn tag command failed.
>>>>> Command output:
>>>>> svn: Path
>>>>>
>>>>> 'https://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-2.6'
>>>>> already exists
>>>>>
>>>>> What's the correct way of re-releaing a plugin that either was stuffed
>>>>> up before a vote or fails the vote?
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Apache Maven
>>> http://twitter.com/jvanzyl
>>> ----------------------------------------------------------
>>>
>>> You are never dedicated to something you have complete confidence in.
>>> No one is fanatically shouting that the sun is going to rise tomorrow.
>>> They know it is going to rise tomorrow. When people are fanatically
>>> dedicated to political or religious faiths or any other kind of
>>> dogmas or goals, it's always because these dogmas or
>>> goals are in doubt.
>>>
>>> -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ----------------------------------------------------------
>
> People develop abstractions by generalizing from concrete examples.
> Every attempt to determine the correct abstraction on paper without
> actually developing a running system is doomed to failure. No one
> is that smart. A framework is a resuable design, so you develop it by
> looking at the things it is supposed to be a design of. The more examples
> you look at, the more general your framework will be.
>
> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Re-Releasing plugin steps.
Posted by Jason van Zyl <jv...@sonatype.com>.
I can just release it with the current version no?
When are you going to release scm?
On 23-Mar-09, at 9:00 AM, Olivier Lamy wrote:
> this need a maven-scm release before.
> It's on my todo list.
>
> --
> Olivier
>
> 2009/3/23 Jason van Zyl <jv...@sonatype.com>:
>> I'm going to stage the release plugin tonight.
>>
>> On 23-Mar-09, at 6:07 AM, Olivier Lamy wrote:
>>
>>> Hi,
>>> A very famous issue ! http://jira.codehaus.org/browse/MRELEASE-375
>>>
>>> My next days jobs will be releasing maven-scm and release-
>>> plugin :-))
>>>
>>> --
>>> Olivier
>>>
>>> 2009/3/23 Barrie Treloar <ba...@gmail.com>:
>>>>
>>>> http://maven.apache.org/developers/release/releasing.html
>>>>
>>>> Step 6. Verify the Staged artifacts
>>>>
>>>> Indicates that if I dont like the contents I can drop the
>>>> repository
>>>> and rollback the release.
>>>>
>>>> If I then try release:prepare again I get a failure:
>>>>
>>>> [INFO] Working directory: D:\ide\maven\maven-eclipse-plugin
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [ERROR] BUILD FAILURE
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Unable to tag SCM
>>>> Provider message:
>>>> The svn tag command failed.
>>>> Command output:
>>>> svn: Path
>>>> 'https://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-2.6'
>>>> already exists
>>>>
>>>> What's the correct way of re-releaing a plugin that either was
>>>> stuffed
>>>> up before a vote or fails the vote?
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ----------------------------------------------------------
>>
>> You are never dedicated to something you have complete confidence in.
>> No one is fanatically shouting that the sun is going to rise
>> tomorrow.
>> They know it is going to rise tomorrow. When people are fanatically
>> dedicated to political or religious faiths or any other kind of
>> dogmas or goals, it's always because these dogmas or
>> goals are in doubt.
>>
>> -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more
examples
you look at, the more general your framework will be.
-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Re-Releasing plugin steps.
Posted by Olivier Lamy <ol...@apache.org>.
this need a maven-scm release before.
It's on my todo list.
--
Olivier
2009/3/23 Jason van Zyl <jv...@sonatype.com>:
> I'm going to stage the release plugin tonight.
>
> On 23-Mar-09, at 6:07 AM, Olivier Lamy wrote:
>
>> Hi,
>> A very famous issue ! http://jira.codehaus.org/browse/MRELEASE-375
>>
>> My next days jobs will be releasing maven-scm and release-plugin :-))
>>
>> --
>> Olivier
>>
>> 2009/3/23 Barrie Treloar <ba...@gmail.com>:
>>>
>>> http://maven.apache.org/developers/release/releasing.html
>>>
>>> Step 6. Verify the Staged artifacts
>>>
>>> Indicates that if I dont like the contents I can drop the repository
>>> and rollback the release.
>>>
>>> If I then try release:prepare again I get a failure:
>>>
>>> [INFO] Working directory: D:\ide\maven\maven-eclipse-plugin
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD FAILURE
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Unable to tag SCM
>>> Provider message:
>>> The svn tag command failed.
>>> Command output:
>>> svn: Path
>>> 'https://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-2.6'
>>> already exists
>>>
>>> What's the correct way of re-releaing a plugin that either was stuffed
>>> up before a vote or fails the vote?
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ----------------------------------------------------------
>
> You are never dedicated to something you have complete confidence in.
> No one is fanatically shouting that the sun is going to rise tomorrow.
> They know it is going to rise tomorrow. When people are fanatically
> dedicated to political or religious faiths or any other kind of
> dogmas or goals, it's always because these dogmas or
> goals are in doubt.
>
> -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Re-Releasing plugin steps.
Posted by Jason van Zyl <jv...@sonatype.com>.
I'm going to stage the release plugin tonight.
On 23-Mar-09, at 6:07 AM, Olivier Lamy wrote:
> Hi,
> A very famous issue ! http://jira.codehaus.org/browse/MRELEASE-375
>
> My next days jobs will be releasing maven-scm and release-plugin :-))
>
> --
> Olivier
>
> 2009/3/23 Barrie Treloar <ba...@gmail.com>:
>> http://maven.apache.org/developers/release/releasing.html
>>
>> Step 6. Verify the Staged artifacts
>>
>> Indicates that if I dont like the contents I can drop the repository
>> and rollback the release.
>>
>> If I then try release:prepare again I get a failure:
>>
>> [INFO] Working directory: D:\ide\maven\maven-eclipse-plugin
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Unable to tag SCM
>> Provider message:
>> The svn tag command failed.
>> Command output:
>> svn: Path 'https://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-2.6'
>> already exists
>>
>> What's the correct way of re-releaing a plugin that either was
>> stuffed
>> up before a vote or fails the vote?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------
You are never dedicated to something you have complete confidence in.
No one is fanatically shouting that the sun is going to rise tomorrow.
They know it is going to rise tomorrow. When people are fanatically
dedicated to political or religious faiths or any other kind of
dogmas or goals, it's always because these dogmas or
goals are in doubt.
-- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Re-Releasing plugin steps.
Posted by Stephen Connolly <st...@gmail.com>.
2009/3/23 Barrie Treloar <ba...@gmail.com>
> On Mon, Mar 23, 2009 at 11:37 PM, Olivier Lamy <ol...@apache.org> wrote:
> > Hi,
> > A very famous issue ! http://jira.codehaus.org/browse/MRELEASE-375
> >
> > My next days jobs will be releasing maven-scm and release-plugin :-))
>
> yes i saw that but didn't click that running the below command with
> 1.5.6 was hanging becuase of it...
>
> Upgrading to 1.6.0 svn fixes the manual delete issue:
>
> But mvn release:prepare still failed (using svn 1.6.0).
>
> Do you know why that is?
>
Because when you use the neon transport for a http or a https based
repository, there is a bug in neon that prevents tagging from the working
copy unless the working copy is at the head revision.
You could do any of the following:
1. Switch to using the dav_serf for your http or https repository (This is
reported to work but I have not had an oportunity to test it)
2. Use a script something like this
mvn release:prepare release:perform $*
svn update
mvn release:prepare release:perform $*
You can make the script all fancy checking return values and searching the
release.properties file for one of the two phases where it breaks (scm-tag
and another phase which I do not have to hand)
I'll post my unix and windows scripts for running a release when I get into
work tomorrow.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Re-Releasing plugin steps.
Posted by Barrie Treloar <ba...@gmail.com>.
On Mon, Mar 23, 2009 at 11:37 PM, Olivier Lamy <ol...@apache.org> wrote:
> Hi,
> A very famous issue ! http://jira.codehaus.org/browse/MRELEASE-375
>
> My next days jobs will be releasing maven-scm and release-plugin :-))
yes i saw that but didn't click that running the below command with
1.5.6 was hanging becuase of it...
Upgrading to 1.6.0 svn fixes the manual delete issue:
But mvn release:prepare still failed (using svn 1.6.0).
Do you know why that is?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Re-Releasing plugin steps.
Posted by Olivier Lamy <ol...@apache.org>.
Hi,
A very famous issue ! http://jira.codehaus.org/browse/MRELEASE-375
My next days jobs will be releasing maven-scm and release-plugin :-))
--
Olivier
2009/3/23 Barrie Treloar <ba...@gmail.com>:
> http://maven.apache.org/developers/release/releasing.html
>
> Step 6. Verify the Staged artifacts
>
> Indicates that if I dont like the contents I can drop the repository
> and rollback the release.
>
> If I then try release:prepare again I get a failure:
>
> [INFO] Working directory: D:\ide\maven\maven-eclipse-plugin
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Unable to tag SCM
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Path 'https://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-2.6'
> already exists
>
> What's the correct way of re-releaing a plugin that either was stuffed
> up before a vote or fails the vote?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org