OK, so In am currenty performing a major refactoring of
versions-maven-plugin...
I'm looking for some feedback from anyone using this plugin....
Specifically anyone using the update-properties goal...
I have just finished a bit of refactoring (on my branch not trunk) that
associates a property with *all* dependencies that specify their version
using the property value... so thus:
<dependency>
<groupId>foo</groupId>
<artifactId>bar-core</artifactId>
<version>${bar-version}</version>
</dependency>
<dependency>
<groupId>foo</groupId>
<artifactId>bar-logging</artifactId>
<version>${bar-version}</version>
</dependency>
<dependency>
<groupId>foo</groupId>
<artifactId>bar-extn</artifactId>
<version>${bar-version}</version>
</dependency>
...
<properties>
<bar-version>1.0</bar-version>
</properyties>
will result in an association with all three artifacts, and the property
will be updated to the highest *common* version... whereas at the moment it
just associates the first property (which could be at a higher versions than
the others)
Also, it now correctly associates plugins with the plugin repository, so
that if your pluginRepository has a smaller subset of bar-maven-plugin that
will also control what version gets used (assuming that the plugin version
is controlled by ${bar-version})
Now for the fun.....
profiles....
what should I do with the damn profiles....
At present all properties will be updated irrespective of where they are...
but I'm thinking this might not be quite so good an idea...
the simplest solution for me is to update all properties in *active*
profiles, and leave inactive profiles alone... this would also have the side
effect of not picking up associations from the inactive profiles...
Has anyone any good objections to this approach? Or suggestions for
alternative approaches?
