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
