You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Rainer Jung <ra...@kippdata.de> on 2010/10/21 23:14:24 UTC

Changes to jk release script

To simplify Mladen's plan to use RCs for jk release, but not including 
the RC name in the tarballs I adjusted the jk release script a bit:

- flag "-t" is now "-v" for "version" and works as before

- new optional flag "-t" allows to explicitely give a tag from which to 
release in case the default tag is not the right one. The default tag is 
JK_MAJOR_MIDDLE_MINOR. So e.g. for using an RC1 for 1.2.31 one would do

jkrelease.sh -v 1.2.31 -t JK_1_2_31_RC_1

or whatever the name of the tag was. For the default tag it would simply 
still be

jkrelease.sh -v 1.2.31

The script checks, whether a given tag starts with the right version. If 
one chooses a really strange tag name, one can force its use with "-f".

To be able to detect an unofficial RC out in the wild, the subversion 
revision number used for rolling the tarball will be logged as part of 
the startup log message in addition to the normal version.

Regards,

Rainer


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org