ansaurus

Question

Publishing POMs via Maven and inserting build version info

Answer 1

+2 A:

I wouldn't use this approach because it makes building a project checked out from the SCM not possible without providing the build.number property. I don't think that this is a good thing. Maybe I'm missing something though.

Actually, I don't get what you are trying to achieve exactly (why don't you write the build number in the manifest for example). But, according to the Maven Features on the Teamcity website:

By default, it also keeps TeamCity build number in sync with the Maven version number (...).

Couldn't that be helpful? There is another thread about this here.

Pascal Thivent 2010-02-02 11:12:18

I can build a project checked out by providing a default profile with a build.number of 'NONE' (or similar), and my TeamCity build uses a different profile that uses the TeamCity property. Does that address your first concern.My core build is deploying a pom.xml alone. I'd like to change that, then get TeamCity to build/deploy to a new build number and change the version *within* the deployed pom.xml. Does that make sense ? I'll check out that link, though.

Brian Agnew 2010-02-02 11:18:37

@Brian While I like the SNAPSHOT mechanism (but that's another story), the profile trick will work for the first point. Regarding the second point, I'm not sure to get everything. I usually use the release plugin to change the version, create a branch, etc. I'll think about this.

Pascal Thivent 2010-02-02 11:41:22

@Pascal - thx. My Maven knowledge is strictly limited.

Brian Agnew 2010-02-02 12:03:42

@Pascal Good answer. Brain, it looks as if you try to work just in the opposite direction. The Maven pom should provide the version number for your product (as it is planned for releasing). Use the release-plug-in to create the (final) release (so without SNAPSHOT). TeamCity can add a build-number somewhere (in logging and in the created jar MANIFEST.MF). But it should not be used as the version number for your product.

Verhagen 2010-02-14 10:42:25

Answer 2

A:

Try to use generateReleasePoms property of maven-realease-plugin, maybe that helps a little.

cetnar 2010-02-03 12:04:01

ansaurus

tags:

views:

answers:

Publishing POMs via Maven and inserting build version info

related questions