[
http://jira.codehaus.org/browse/MRELEASE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134755#action_134755
]
Sam De Block commented on MRELEASE-310:
---------------------------------------
This also conflicts when using M2Eclipse, because then you dont even have a
separate maven install.
Basically this plugin doesnt work when maven is launched through the maven
embedder.
> ForkedMavenExecutor assumes mvn is on command-line path
> -------------------------------------------------------
>
> Key: MRELEASE-310
> URL: http://jira.codehaus.org/browse/MRELEASE-310
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-7
> Reporter: Brian Jackson
> Attachments: ForkedMavenExecutor.patch
>
>
> The ForkedMavenExecutor assumes the mvn executable is on the command-line
> path. This will cause the release goals to fail if mvn is run from an
> explicit path and the PATH environment variable has not be set to contain a
> mvn executable. More dangerously though is the case where the release goal
> is started with an explicit mvn executable of one version (for instance
> 2.0.8) but a different version of the mvn executable is available on the
> PATH. The forked processes will run a different version of Maven2 that the
> parent process.
--
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
