logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <ralph.go...@dslextreme.com>
Subject Re: [Vote] Log4j 2.0-alpha1 rc1
Date Sun, 22 Jul 2012 19:58:38 GMT
I agree, but you can't do that with the release plugin.  If you want artifacts named 2.0-alpha1
you are going to get a tag named 2.0-alpha1 and there is no way to get it to create a tag
with 2.0-alpha1-rc1.  The only options I see are a) delete the tag after the release fails,
b) rename the tag to -rcn after the release fails, or c) rename the tag to -rcn before the
vote and then rename it to remove -rcn after it succeeds.

If you have other ideas please let me know.

Note that the documentation on the Commons Wiki regarding using the release plugin doesn't
document how to use Nexus.  AFAIK, most commons projects don't use the release plugin.

Ralph 



On Jul 22, 2012, at 12:38 PM, Gary Gregory wrote:

> I see now, the problem is that the tag is incorrectly named. The tag for RC1
> 
> https://svn.apache.org/repos/asf/logging/log4j/log4j2/tags/log4j-2.0-alpha1/
> 
> should have been:
> 
> https://svn.apache.org/repos/asf/logging/log4j/log4j2/tags/log4j-2.0-RC1/
> 
> Then you can have:
> 
> https://svn.apache.org/repos/asf/logging/log4j/log4j2/tags/log4j-2.0-RC2/
> 
> and so on.
> 
> Once the vote passes, you create:
> 
> https://svn.apache.org/repos/asf/logging/log4j/log4j2/tags/log4j-2.0/
> 
> At least, that's the process we have in Commons.
> 
> Gary
> 
> 
> On Sun, Jul 22, 2012 at 3:32 PM, Ralph Goers <ralph.goers@dslextreme.com> wrote:
> No.  After the release fails I delete the tag.  Rerunning the release plugin is going
to create it again. If I don't delete it the re-release will fail.
> 
> Ralph
> 
> On Jul 22, 2012, at 12:24 PM, Gary Gregory wrote:
> 
>> That's all fine but are you saying that it is the release plugin removing the tag
from SVN? Or some other plugin?
>> 
>> Gary
>> 
>> On Sun, Jul 22, 2012 at 2:53 PM, Ralph Goers <ralph.goers@dslextreme.com> wrote:
>> No, we are talking about the same thing.
>> 
>> I use the release plugin to do a release.  It asks me what version I want for the
artifacts and I tell it 2.0-alpha1.  It then updates all the artifacts with that version and
uses that version to create the svn tag.  I don't know of a way to get the release plugin
to create the artifacts with the correct release version yet create a tag with -rcn.  If you
do please let me know how to do it.
>> 
>> FWIW, this is the same process I used when I released commons-vfs 2.0.
>> 
>> Ralph
>> 
>> On Jul 22, 2012, at 10:55 AM, Gary Gregory wrote:
>> 
>>> Hi Ralph,
>>> 
>>> I do not think we are talking about the same thing because I do not understand
your reply. 
>>> 
>>> Right now, if I want to look at the code that the RC1, I cannot. The point of
the tag is to have a record of the code as we take each vote. 
>>> 
>>> That's because the snapshot created the SVN tag is gone. It looks like it was
created for the vote but it no longer exists. 
>>> The requested URL /repos/asf/logging/log4j/log4j2/tags/log4j-2.0-alpha1/ was
not found on this server.
>>> 
>>> Such tags should never deleted. 
>>> 
>>> Gary
>>> 
>>> On Jul 22, 2012, at 11:03, Ralph Goers <rgoers@apache.org> wrote:
>>> 
>>>> Please go back and look at my earlier message from before the release. That
is exactly what I do. Otherwise all the artifacts will have an rc in their versions and be
useless.
>>>> 
>>>> Sent from my iPad
>>>> 
>>>> On Jul 22, 2012, at 5:28 AM, Gary Gregory <garydgregory@gmail.com>
wrote:
>>>> 
>>>>> The tag looks to be gone. Can anyone see it? We should never delete a
tag when a vote passes or fails.
>>>>> 
>>>>> Gary
>>>>> 
>>>>> On Sun, Jul 15, 2012 at 2:44 AM, Ralph Goers <ralph.goers@dslextreme.com>
wrote:
>>>>> This is a vote to release Log4j 2.0-alpha1, which will be the first release
of Log4j 2.0.
>>>>> 
>>>>> Tag:
>>>>> https://svn.apache.org/repos/asf/logging/log4j/log4j2/tags/log4j-2.0-alpha1/
>>>>> 
>>>>> Web site:
>>>>> http://people.apache.org/~rgoers/log4j2/
>>>>> 
>>>>> Artifacts:
>>>>> Nexus Staging Location: https://repository.apache.org/content/repositories/orgapachelogging-050/

>>>>> 	Each of the artifacts below will be located in the location of its Maven
coordinates. For example, log4j-core-2.0-alpha1.jar is located at org/apache/logging/log4j/log4j-core/2.0-alpha1/log4j-core-2.0-alpha1.jar,
under the Nexus staging location.
>>>>> 
>>>>> Description:
>>>>> 
>>>>> Log4j 2.0-alpha1
>>>>> 
>>>>> Details:
>>>>> 
>>>>> The following artifacts have been staged to the org.apache.logging-050
(u:rgoers, a:99.180.69.21) repository.
>>>>> 
>>>>> archetype-catalog.xml
>>>>> log4j-flume-ng-2.0-alpha1-javadoc.jar
>>>>> log4j-flume-ng-2.0-alpha1-tests.jar.asc
>>>>> log4j-flume-ng-2.0-alpha1-javadoc.jar.asc
>>>>> log4j-flume-ng-2.0-alpha1-sources.jar.asc
>>>>> log4j-flume-ng-2.0-alpha1.jar.asc
>>>>> log4j-flume-ng-2.0-alpha1.jar
>>>>> log4j-flume-ng-2.0-alpha1.pom
>>>>> log4j-flume-ng-2.0-alpha1-sources.jar
>>>>> log4j-flume-ng-2.0-alpha1-tests.jar
>>>>> log4j-flume-ng-2.0-alpha1.pom.asc
>>>>> log4j-jcl-2.0-alpha1-sources.jar
>>>>> log4j-jcl-2.0-alpha1.pom.asc
>>>>> log4j-jcl-2.0-alpha1-sources.jar.asc
>>>>> log4j-jcl-2.0-alpha1-javadoc.jar.asc
>>>>> log4j-jcl-2.0-alpha1.jar
>>>>> log4j-jcl-2.0-alpha1.pom
>>>>> log4j-jcl-2.0-alpha1.jar.asc
>>>>> log4j-jcl-2.0-alpha1-javadoc.jar
>>>>> log4j12-api-2.0-alpha1-javadoc.jar.asc
>>>>> log4j12-api-2.0-alpha1-sources.jar
>>>>> log4j12-api-2.0-alpha1-sources.jar.asc
>>>>> log4j12-api-2.0-alpha1.jar
>>>>> log4j12-api-2.0-alpha1.pom.asc
>>>>> log4j12-api-2.0-alpha1-javadoc.jar
>>>>> log4j12-api-2.0-alpha1.pom
>>>>> log4j12-api-2.0-alpha1.jar.asc
>>>>> log4j-distribution-2.0-alpha1-bin.zip.asc
>>>>> log4j-distribution-2.0-alpha1-src.zip
>>>>> log4j-distribution-2.0-alpha1-bin.zip
>>>>> log4j-distribution-2.0-alpha1.pom
>>>>> log4j-distribution-2.0-alpha1-src.zip.asc
>>>>> log4j-distribution-2.0-alpha1-src.tar.gz.asc
>>>>> log4j-distribution-2.0-alpha1-src.tar.gz
>>>>> log4j-distribution-2.0-alpha1-bin.tar.gz.asc
>>>>> log4j-distribution-2.0-alpha1-bin.tar.gz
>>>>> log4j-distribution-2.0-alpha1.pom.asc
>>>>> log4j-2.0-alpha1.pom
>>>>> log4j-2.0-alpha1.pom.asc
>>>>> log4j-core-2.0-alpha1-javadoc.jar
>>>>> log4j-core-2.0-alpha1.pom
>>>>> log4j-core-2.0-alpha1.pom.asc
>>>>> log4j-core-2.0-alpha1-tests.jar.asc
>>>>> log4j-core-2.0-alpha1-sources.jar
>>>>> log4j-core-2.0-alpha1-tests.jar
>>>>> log4j-core-2.0-alpha1-sources.jar.asc
>>>>> log4j-core-2.0-alpha1-javadoc.jar.asc
>>>>> log4j-core-2.0-alpha1.jar.asc
>>>>> log4j-core-2.0-alpha1.jar
>>>>> log4j-api-2.0-alpha1.jar.asc
>>>>> log4j-api-2.0-alpha1.pom
>>>>> log4j-api-2.0-alpha1-javadoc.jar.asc
>>>>> log4j-api-2.0-alpha1-sources.jar
>>>>> log4j-api-2.0-alpha1-sources.jar.asc
>>>>> log4j-api-2.0-alpha1.jar
>>>>> log4j-api-2.0-alpha1-javadoc.jar
>>>>> log4j-api-2.0-alpha1.pom.asc
>>>>> slf4j-impl-2.0-alpha1-sources.jar.asc
>>>>> slf4j-impl-2.0-alpha1.pom
>>>>> slf4j-impl-2.0-alpha1-javadoc.jar
>>>>> slf4j-impl-2.0-alpha1.jar
>>>>> slf4j-impl-2.0-alpha1.jar.asc
>>>>> slf4j-impl-2.0-alpha1-javadoc.jar.asc
>>>>> slf4j-impl-2.0-alpha1-sources.jar
>>>>> slf4j-impl-2.0-alpha1.pom.asc
>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> E-Mail: garydgregory@gmail.com | ggregory@apache.org 
>>>>> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
>>>>> Spring Batch in Action: http://bit.ly/bqpbCK
>>>>> Blog: http://garygregory.wordpress.com 
>>>>> Home: http://garygregory.com/
>>>>> Tweet! http://twitter.com/GaryGregory
>>> 
>> 
>> 
>> 
>> 
>> -- 
>> E-Mail: garydgregory@gmail.com | ggregory@apache.org 
>> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
>> Spring Batch in Action: http://bit.ly/bqpbCK
>> Blog: http://garygregory.wordpress.com 
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
> 
> 
> 
> 
> -- 
> E-Mail: garydgregory@gmail.com | ggregory@apache.org 
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com 
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory


Mime
View raw message