[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9268) Align versions across poms on each module
Max Rydahl Andersen (JIRA)
jira-events at lists.jboss.org
Wed Jul 27 11:56:23 EDT 2011
[ https://issues.jboss.org/browse/JBIDE-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617085#comment-12617085 ]
Max Rydahl Andersen commented on JBIDE-9268:
--------------------------------------------
For those interested i'm using this script in each module and then rebuilding and manually verifying the fixes are correct/sane before committing.
echo Changing feature versions to $1.qualifier
exp='s/version=".*.qualifier"/version="'$1'.qualifier"/g'
find . -name feature.xml -exec perl -p -e $exp -i.bak {} \;
echo Removing superflous version in child modules
find . -name pom.xml -mindepth 2 -maxdepth 3 -exec perl -p -i.bak -e 'undef $/; s/(parent.*parent\>.*?)(\<version.*?version\>)/\1/ms' {} \;
echo Changing 0.0.1-SNAPSHOT to $1-SNAPSHOT in pom.xmls
exp='s/0.0.1-SNAPSHOT/'$1'-SNAPSHOT/g'
find . -name pom.xml -exec perl -p -e $exp -i {} \;
echo Changing Bundle-Version: .*.qualifier to $1.qualifier in manifest.mf
exp="s/Bundle-Version: .*.qualifier/Bundle-Version: $1.qualifier/g"
find . -name MANIFEST.MF -maxdepth 4 -exec perl -p -i.bak -e "$exp" {} \;
> Align versions across poms on each module
> -----------------------------------------
>
> Key: JBIDE-9268
> URL: https://issues.jboss.org/browse/JBIDE-9268
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, Cleanup
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 3.3.0.M3
>
>
> We recently aligned the pom's within each jboss tools module svn to have "natural parents" meaning the only pom within a module that refers the parent pom is the "root" one.
> i.e. hibernatetools/pom.xml instead of *all* plugins and features inside the module.
> That made updating parent pom's easy, now we should just get the pom versions aligned within the module to allow easy update of versions in that module without manual tweaking of files.
> What this allows is that you can use commands like this:
> mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=3.4.0-SNAPSHOT
> and tycho will take care of updating all pom/manifest/feature.xml/product defs for that module subdirectory.
> (if the references are *outside* that directory then of course things won't be updated automatically)
> The changes i'm planning will do two things:
> 1) Align all versions within one module (that is needed for the one command version update)
> 2) Remove all redundant <version> references when the parent reference is enough.
> Please note, that if a module owner wish to manage individual plugin versions that is perfectly still doable
> they just need to add the explicit <version> reference and cannot rely on the one command version update
> to work automatically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list