> Hi,
> We noticed some strange behaviour when switching to Maven 2.0.9. The
> background is:
>
> We have a patch for maven-javadoc-plugin that we applied internally
> and built a new version - 2.4.1 (while wating for the official 2.5
> release with our patch applied).
> The 2.4.1 version is deployed to our internal repo (maintained using
> Archiva) and coexists along with version 2.4. The metadata files are
> fine (since 2.4.1 version was deployed using mvn deploy).
>
> The javadoc-plugin was initially defined in our reporting section:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-javadoc-plugin</artifactId>
> <version>2.4</version>
> <configuration>
> <aggregate>true</aggregate>
> </configuration>
> </plugin>
>
> After we created the new javadoc plugin version 2.4.1 we changed that
> in the above version definition. But instead of using the new version
> Maven 2.0.9 insisted on using the 2.4 version
> defined in the root maven pom.xml
> Is this normal? We know that the plugin version defaults were added in
> Maven 2.0.9, but shouldn't they be used only if no version definition
> is present?
>
> At the end, we were able to override the version in the root maven pom
> by defining our version in our own pluginManagement section.
>
> Regards,
> Detelin
>
>
