geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Kirby (JIRA)" <>
Subject [jira] Resolved: (GERONIMO-4274) Automate version numbers in README and RELASE_NOTES files
Date Sun, 31 Aug 2008 17:21:44 GMT


Ted Kirby resolved GERONIMO-4274.

    Resolution: Fixed

Done with rev 690735

In GERONIMODEVTOOLS-505, I did some automated release number processing, and I have applied
similar automation to the server README and RELEASE_NOTES files.  If folks like it, this could
be applied to the 2.1 branch.  If not, it can be reverted! :-)

Since the ant copy task is used to process the .txt files, I created an ant filter to set
the VERSION token to ${pom.version}.
@VERSION@ is used in the .txt files.  (This could easily be changed to ${VERSION} if desired.)
The assemblies/geronimo-boilerplate/pom.xml file is changed to process RELEASE_NOTES-${pom.version}.txt,
thus eliminating that manual change.  The side-effect here is that the RELEASE_NOTE file must
be named RELEASE_NOTES-2.2-SNAPSHOT.txt.  When the version is changed to 2.2, the file must
be renamed.

With this change, assemblies/geronimo-boilerplate/pom.xml does not have to be changed at all,
and manual version number changes to README and RELEASE_NOTES are eliminated.

> Automate version numbers in README and RELASE_NOTES files
> ---------------------------------------------------------
>                 Key: GERONIMO-4274
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 2.2
>            Reporter: Ted Kirby
>            Assignee: Ted Kirby
>             Fix For: 2.2
> Minimize the manual editing required in the .txt and pom.xml files when release numbers

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message