[
https://issues.apache.org/jira/browse/MJAVADOC-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957381#comment-17957381
]
Olivier Lamy commented on MJAVADOC-261:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[olamy/maven-javadoc-plugin#402|https://github.com/olamy/maven-javadoc-plugin/issues/402].
> 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: https://issues.apache.org/jira/browse/MJAVADOC-261
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.6
> Environment: Bamboo build server with several M2 installations
> Reporter: Michael Robinson
> Assignee: Benjamin Bentmann
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
