[ 
http://jira.codehaus.org/browse/MJAVADOC-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190667#action_190667
 ] 

Michael Robinson commented on MJAVADOC-261:
-------------------------------------------

That sucks because now it is a pain to have the build server pull double duty 
as much of anything else because mvn want be available on a the PATH.

What seems worse though is that the build doesn't seem as portable across 
environments. Before I pinned down the plugin version it just figured out which 
version to use (even if it was wrong based on the env) but now it fails the 
build entirely with an erroneous error.

The only reason I really went and pinned the version is b/c of the maven 
embedder 3.x (from m2_eclipse) complaining about it... 

> 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
>            Assignee: Benjamin Bentmann
>         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

        

Reply via email to