[ http://issues.apache.org/jira/browse/PLUTO-259?page=all ]
Elliot Metsger updated PLUTO-259:
---------------------------------
Attachment: PLUTO-259-firstattempt.patch
expectedResults.properties, environment.properties are now interpolated during
the maven lifecycle using properties set in the parent pom.
pluto-portal-driver-config.xml is interpolated as well, but using a snapshot
version of the maven-war-plugin. If the war plugin isn't released soon, the
portal code could be updated to search for the driver config on the classpath,
which would allow it to be interpolated like the other .properties files (by
being placed in src/main/resources).
I patched dist-build.xml to require the pluto.version property be set on the
command line.
The pom versions would be updated automatically if the maven release plugin is
used.
Assuming the maven release plugin is used, the pluto release would go something
like:
1. Manually update <properties> in the parent pom.xml in the trunk working copy.
2. release:prepare, release:perform on the working copy which will tag the
release in SVN with correct version numbers
3. Then, 'svn export' the newly created tag
4. Use ant -f dist-build.xml -Dpluto.version=1.1.0 to build the source and
binary release packages for the tag.
There's got to be a better way of sharing properties between the ant build and
the maven poms.... will continue to dig.
This patch depends on a snapshot version of the maven-war-plugin, so not
suitable to be applied yet.
> 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
