On 04/03/2007, at 1:51 AM, Dennis Lundberg wrote:
Is that because maven-plugin-descriptor-2.0.5.jar is in M2_HOME/lib ?
yes
How does plugin updates work in a situation like this? Say we have
a user that is running maven 2.0.4. He/she issues "mvn -U site" on
a project that requires maven-plugin-plugin-2.3, which in turn has
2.0.5 as a prerequisite.
1. Does maven-plugin-plugin-2.3 get downloaded?
2. Does maven-plugin-plugin-2.3 get used by maven 2.0.4 if it has
been downloaded or installed locally?
No and no. The logic is:
a) use the version requested in the POM (if you don't match the
prerequisite, the build will fail)
b) use the latest version as defined by the repository. If, on
downloading the POM, the latest version fails a prerequisite, use
'(,latest)' and so on (ie, look for the latest plugin that does match
the prerequisite).
This is the reason to update it - people grabbing snapshots on 2.0.4
had their build fail because it tried to use 2.3-SNAPSHOT
unsuccessfully. Adding the pre-req means 2.0.4 users will ignore the
new plugin and stay on 2.2.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
