Hi Dave,
I haven’t tried that plugin myself, but I think the idea of it is that it “always runs” while editing code.
It decorates the project explorer with problem markers; so you should fix those before committing a change that affects versions.
you don’t run that plugin separately and you can’t integrate it with the build.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River
direct +43.662.457915.85 fax +43.662.457915.6
From: tm-dev-bounces@xxxxxxxxxxx
[mailto:tm-dev-bounces@xxxxxxxxxxx] On Behalf Of David Dykstal
Sent: Tuesday, June 04, 2013 5:28 PM
To: TM project developer discussions
Subject: Re: [tm-dev] FW: [eclipse-dev] POM Version tool moved to Releng Tools
So this is something that we would run prior to a commit.
We should probably get into the habit of correctly updating version numbers in the first commit for a plugin after a release. I see several cases in the log where we updated the version numbers in a separate commit.
Hi all,
Remember that we discussed issues with POM.XML versions not matching MANIFEST.MF in the TM build ?
Here’s a tool from the Eclipse Platform / PDE team, to make sure that the versions in MANIFEST.MF and POM.XML match.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect
– Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6
Hi,
The POM Version tool will warn you if the artifact version in a POM file (pom.xml) does not match the bundle version in the manifest (manifest.mf). Having different versions
in a bundle will cause the Eclipse builder to fail.
The tool was originally added to the PDE builder, but for the Kepler release it has been moved to Eclipse Releng Tools. Eclipse Releng Tools can be installed from the Eclipse
Project Updates p2 repository (http://download.eclipse.org/eclipse/updates/4.3-I-builds/).
The POM Version tool is off by default. Go to Preferences > POM Version Tool and change the severity to error or warning to enable it for your workspace.
Curtis