Rick,
Not any such tool I’m aware of, but for updating the release string for next release, what I’m used to doing is just a single command of combined find/grep/sed for your reference, for example updating 2.6.0 to 2.7.0:
find . -type f -name "antbuild.properties" -o -name "build.properties" -o -name "pom.xml" -o -name "antbuild.xml" -o -name "MANIFEST.MF" –o –name “autobuild.properties” |xargs grep "2\.6\.0" |cut -f1 -d":" |xargs sed -i 's/2\.6\.0/2.7.0/g'
Liu Bo
From: Rick Curtis [mailto:curtisr7@xxxxxxxxx]
Sent: Wednesday, May 06, 2015 23:34
To: Dev mailing list for Eclipse Persistence Services
Cc: Bo Liu
Subject: EclipseLink release process
All -
I'm looking at trying to create a 2.6.0_WAS tag and was wondering if there is a script or something that will update all of the versions fields in EclipseLink artifacts after tagging a maintenance release? For example, I see in most of the modules there is a version(2.6.0/2.6.0_WAS) that needs to updated in [module]/pom.xml, [module]/META-INF/MANIFEST.MF, and [module]/antbuild.properties.
