[
http://jira.codehaus.org/browse/MRELEASE-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190522#action_190522
]
Frederic commented on MRELEASE-359:
-----------------------------------
Do I understand that the mavenExecutorId could be a way that the release plugin
runs without forking a maven to support it's integration when it is launched
through the maven embedder?
Does not seems to work for me with through m2e using maven-release-plugin
2.0-beta-9
see: http://jira.codehaus.org/browse/MRELEASE-310
> Release plugin depends on mvn being in the path of the shell that started the
> current build
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-359
> URL: http://jira.codehaus.org/browse/MRELEASE-359
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Affects Versions: 2.0-beta-7
> Reporter: John Casey
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.0-beta-8
>
>
> It's impossible to run a project release from an environment that uses maven
> without putting it in the path environment variable. This causes problems
> with build servers like Hudson, where you want to be able to configure on a
> project-by-project basis the version of Maven being used. The only
> alternative is to choose a version of Maven to put into the shell environment
> PATH used to start the appserver.
--
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
