maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MINVOKER-41) NullPointerException in InvokerMojo::runBuild in case the mvn executable is not at the expected location
Date Tue, 01 Jul 2008 13:37:27 GMT

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

Jeremy commented on MINVOKER-41:
--------------------------------

Simple. I use the maven2 Ubuntu package. I don't know how it has been built. But what I've
seen is that most of the Maven stuffs are installed in the "/usr/share/maven2" directory.
But the "mvn" executable is put in "/usr/bin", while it is expected to be found in the "/usr/share/maven2/bin"
directory, along with the rest of Maven.
The workaround is as easy as a "ln -s /usr/bin/mvn /usr/share/maven2/bin/mvn".

> NullPointerException in InvokerMojo::runBuild in case the mvn executable is not at the
expected location
> --------------------------------------------------------------------------------------------------------
>
>                 Key: MINVOKER-41
>                 URL: http://jira.codehaus.org/browse/MINVOKER-41
>             Project: Maven 2.x Invoker Plugin
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: $ mvn --version
> Maven version: 2.0.8
> Java version: 1.6.0_06
> OS name: "linux" version: "2.6.24-19-generic" arch: "i386" Family: "unix"
>            Reporter: Jeremy
>
> Assume that the mvn executable cannot be found at the expected location, then InvokerMojo::runBuild
throws a NullPointerException at line 787 (same line number in the trunk version). Indeed,
looking at InvokerMojo.java, if an exception is catched in the try clause line 777 (from the
invoker.execute method call), then "result" remains unaffected and the method call line 787
fails.
> I attach the InvokerMojo.java file as I get it from the svn repository, a "mvn -e -X
install > log" file and one of the POM that triggers the problem.

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

        

Mime
View raw message