You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Manfred Moser (JIRA)" <ji...@codehaus.org> on 2008/04/01 18:51:58 UTC

[jira] Commented: (MINVOKER-28) Cant find mvn command

    [ http://jira.codehaus.org/browse/MINVOKER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129335#action_129335 ] 

Manfred Moser commented on MINVOKER-28:
---------------------------------------

The attached stack trace was produced with mvn clean install -X -e. If necessary I can supply the pom file for reference. Switching to use the standard apache maven install gets the project to build fine so the issue is clearly related to the mvn command not being found as mentioned above.

> Cant find mvn command
> ---------------------
>
>                 Key: MINVOKER-28
>                 URL: http://jira.codehaus.org/browse/MINVOKER-28
>             Project: Maven 2.x Invoker Plugin
>          Issue Type: Bug
>    Affects Versions: 1.1
>         Environment: Ubuntu Linux Gutsy Gibbon with the Maven 2.0.8 package from debian testing
>            Reporter: Manfred Moser
>         Attachments: invoker.log
>
>
> When running an invoker plugin build a null pointer exception occurs because the mvn command is not found with the above configuration. The issue is that the plugin assumes that the mvn command is in M2_HOME/bin. This is not the case with the maven debian package since it complies to the standards and has the mvn command in /usr/bin where as M2_HOME points to /usr/share/maven2/.

-- 
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