ansaurus

Question

Specify artifact version outside of pom

Answer 1

A:

You should be able to achieve this using maven profiles

Scobal 2010-06-03 15:53:27

Answer 2

A:

Short answer: no. And here are some additional remarks:

It doesn't make much sense to use a "released" version (i.e. non SNAPSHOT) for a branch under CI since released versions are not downloaded again even if a newer version is available.
Released versions should be tagged (e.g. 1.0), maintenance is done is in a branch derived from the tag (e.g. 1.0.1-SNAPSHOT).
If you want to distinguish versions built from different branches, use different versions in the POMs.

Pascal Thivent 2010-06-03 16:47:02

In the maven profile I have the updatePolicy set to always for the development release repo. That should make it always check for newer versions even in the case of a non SNAPSHOT, no?

Adam B 2010-06-03 18:35:42

Adam B 2010-06-03 18:50:47

@Adam First comment: No, artifacts are not supposed to change after being released. You'd have to manually copy/delete the file. Second comment: Yes, I understand that and I agree with the last sentence. For the first part, that's why the release plugin is handy (it will upgrade the version numbers for you).

Pascal Thivent 2010-06-03 19:24:37

Thank you for your help Pascal! Updating the version number is where the problem comes in. If jar A is a dependency of 20 other apps/jars then I have to find and update those poms to the new jar A version. I think the versions plugin can help with the updating part, but what about the finding part? The other question then is what version gets used for the integration build? Depending on when feature branches are created there could be a conflict on the version in the pom. Since the build is done via CI I cannot manually resolve the conflict. Perhaps this justifies its own topic.

Adam B 2010-06-03 19:37:06

@AdamB: Indeed, the version plugin can help to update versions once you *found* them. But it doesn't solve the finding part. Now, back to your initial question, I'd keep the 1.0-SNAPSHOT for the stable development version and use something like 1.0-work-SNAPSHOT for the work branch. Your 60 modules don't need to depend on this version after all.

Pascal Thivent 2010-06-03 21:03:56

Answer 3

A:

I was able to accomplish this by using a property in my POM and then overriding it via the command line.

pom.xml:

 ...
    <version>${artifactVersion}</version>
    <properties>
       <artifactVersion>1.0</artifactVersion>  <!-- default version -->
    </properties>
    ...

Then overriding with mvn -DartifactVersion=1.0-SNAPSHOT package

But Pascal's answer above is more in line with what I was really asking. My solution is more of a workaround I feel.

Adam B 2010-06-03 18:41:20

I'm not sure this will work with inheritance (and that's why I didn't suggest it).

Pascal Thivent 2010-06-03 19:07:32

ansaurus

tags:

views:

answers:

Specify artifact version outside of pom

related questions