Hi Niall,
Niall Pemberton wrote:
> Merci Beaucoup - thats fixed it. Still not sure why it just started
> happening though.
It seems the version of the plugin is not locked:
============ %< =============
~/src/Commons/proper/beanutils $ mvn versions:display-plugin-updates
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'versions'.
[INFO] ------------------------------------------------------------------------
[INFO] Building Commons BeanUtils
[INFO] task-segment: [versions:display-plugin-updates]
[INFO] ------------------------------------------------------------------------
[INFO] [versions:display-plugin-updates {execution: default-cli}]
[INFO]
[INFO] All plugins with a version specified are using the latest versions.
[INFO]
[WARNING] The following plugins do not have their version specified:
[WARNING] maven-resources-plugin ...................... (from super-pom)
2.2
[WARNING] maven-site-plugin .................... (from super-pom)
2.0-beta-5
[INFO]
[INFO] ------------------------------------------------------------------------
============ %< =============
Nevertheless strange, since it should have inherited the version from the
parent. With Maven 2.1.0 you get the same result. However, for Maven 2.0.10
the site plugin seems suddenly locked. Maybe a regression in Maven 2.1.x
and upwards ??
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
