If this update policy was not there yet in mvn 2.0.8 then I am not sure whether this can be the reason. Because this was the sequence in which I worked: 1 parent pom with new surefire version on 2.0.8 2 upgrade to 2.0.9 3 tested again
So if I interpret you correctly then the metadata should have been updated after step 1, because I wasn't using 2.0.9 at that time. Ok, I filed http://jira.codehaus.org/browse/MPH-53 - Rintcius -- View this message in context: http://www.nabble.com/Wrong-output-of-mvn-help%3Adescribe--tp19168212p19214997.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
