OK, some quick questions:
1. why do you need to use properties to control the version of a
plugin? You have a pluginManagement section, and that should be the
only place where you have to specify the plugin's version
2. If you want to use properties, why not add a configuration for the
versions plugin and have it update the version with update-properties?
There is definitely a bug that it is not displaying the interpolated
value when you define the version with a property. So can you please
file a JIRA for that.
If you can email the pom files that you are using...
it should be sufficient to just leave
<project>
<parent>
<groupId>anonymized</groupId>
<artifactId>anonymized</artifactId>
<version>...</version>
</parent>
<groupId>anonymized</groupId>
<artifactId>anonymized</artifactId>
<version>...</version>
<properties>
<!-- need these -->
</properties>
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>...</groupId>
<artifactId>anonymized</artifactId>
<version>...</version>
<!-- you can strip executions and configuration, etc -->
</plugin>
<!-- I'll need all the public plugins you're using -->
</plugins>
</pluginManagement>
<plugins>
<plugin>
<groupId>...</groupId>
<artifactId>anonymized</artifactId>
<version>...</version>
<!-- you can strip executions and configuration, etc -->
</plugin>
<!-- I'll need all the public plugins you're using -->
</plugins>
<!-- you can strip the rest of the build stuff -->
</build>
<reporting>
<!-- only the groupId, artifactId and version detail that you
have, strip the rest -->
</reporting>
<!-- you can strip the rest of your pom -->
</project>
Thanks,
Stephen.
P.S. If you have not got the time to strip your pom.xml files you can
just send them to me directly and I will strip them for you.
2008/10/7 Stephen Connolly <[EMAIL PROTECTED]>:
> can you file a jira and/or share your pom files so I can figure out what's
> up
>
> Sent from my iPod
>
> On 6 Oct 2008, at 23:48, "Edelson, Justin" <[EMAIL PROTECTED]>
> wrote:
>
>> I tried to use the versions:display-plugin-updates mojo for the first
>> time today and it didn't quite work as I expected. Maybe this is due to
>> a bad expectation on my part, maybe not.
>>
>> In my organizational POM, I define a bunch of plugin versions with
>> properties. For example:
>>
>> <properties>
>> ...
>> <plugin.version.site>2.0-beta-7</plugin.version.site>
>> ...
>> </properties>
>>
>> And then I reference these plugins in a pluginManagement section.
>> <pluginManagement>
>> ...
>> <plugin>
>> <groupId>org.apache.maven.plugins</groupId>
>> <artifactId>maven-site-plugin</artifactId>
>> <version>${plugin.version.site}</version>
>> </plugin>
>> ...
>> </pluginManagement>
>>
>> I was expecting that I could run mvn versions:display-plugin-updates and
>> see the cases where I needed to update the properties. However, instead
>> what I see is this output:
>>
>> [INFO] The following plugin updates are available:
>> ...
>> [INFO] maven-site-plugin .............. ${plugin.version.site} ->
>> 2.0-beta-7
>>
>>
>> The only plugin for which this is NOT the case is the enforcer plugin:
>> [INFO] maven-enforcer-plugin .................... 1.0-alpha-3 ->
>> 1.0-alpha-4
>>
>> Is this a bug in the plugin or a problem with how I'm using properties?
>>
>> Thanks,
>>
>> Justin Edelson
>> VP, Platform Engineering
>> MTV Networks Digital
>> 212.846.3220 (o)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
