[
http://jira.codehaus.org/browse/MJAVADOC-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190649#action_190649
]
Benjamin Bentmann commented on MJAVADOC-261:
--------------------------------------------
This is not an issue with the plugin but with the Maven startup script and your
environment. If the var {{M2_HOME}} is set, the scripts use that path to load
Maven, regardless from which Maven installation you invoked the script. You
should simply remove this variable.
> Plugin seems to rely on M2 environment variables for Maven version instead of
> the version of Maven that launched the build.
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: MJAVADOC-261
> URL: http://jira.codehaus.org/browse/MJAVADOC-261
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Environment: Bamboo build server with several M2 installations
> Reporter: Michael Robinson
> Attachments: TEAM-SITE-144.log
>
>
> I currently have the plugin pinned to version 2.6 and launching a build that
> runs the javadoc report with Maven 2.2.1 fails with:
> Error resolving version for 'org.apache.maven.plugins:maven-javadoc-plugin':
> Plugin requires Maven version 2.0.9
> The build server currently has a M2 environment variable that points to Maven
> 2.0.6. Changing this environment variable fixes the problem but it would be
> nice if the plugin honored the version of Maven it was launched with.
> Bamboo build server output attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
