You are viewing a plain text version of this content. The canonical link for it is here.

Posted to pluto-dev@portals.apache.org by "Craig Doremus (JIRA)" <ji...@apache.org> on 2006/12/15 20:27:23 UTC

[jira] Commented: (PLUTO-259) Automate new version numbers for new releases

    [ http://issues.apache.org/jira/browse/PLUTO-259?page=comments#action_12458900 ] 
            
Craig Doremus commented on PLUTO-259:
-------------------------------------

The dist-build.xml Ant build file now grabs the version number from the root pom.xml using the xmlproperty task to set the pluto.version property. Commited in SVN revision 487628.

> Automate new version numbers for new releases
> ---------------------------------------------
>
>                 Key: PLUTO-259
>                 URL: http://issues.apache.org/jira/browse/PLUTO-259
>             Project: Pluto
>          Issue Type: Improvement
>          Components: build system
>    Affects Versions: 1.1.0-beta2, 1.1.0
>            Reporter: Craig Doremus
>         Assigned To: Elliot Metsger
>            Priority: Minor
>             Fix For: 1.1.0
>
>         Attachments: PLUTO-259-firstattempt.patch
>
>
> When a new release is prepared version numbers need to be changed in all pom.xml files, dist-build.xml, the pluto-portal-driver-config.xml in the pluto-portal module, expectedResults.properties in the portal-testsuite module, and environment.properties in pluto-container module. We need to automate that process.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira