You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2003/08/15 11:58:14 UTC
[jira] Updated: (MAVEN-672) NPE when using a different effective working directory

The following issue has been updated:

    Updater: dion gillard (mailto:dion@apache.org)
       Date: Fri, 15 Aug 2003 4:57 AM
    Changes:
             Fix Version changed to 1.0-rc1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-672&page=history

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-672


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-672
    Summary: NPE when using a different effective working directory
       Type: Bug

     Status: Unassigned
   Priority: Minor

 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
   Fix Fors:
             1.0-rc1
   Versions:
             1.0-beta-10
             1.0-rc1

   Assignee: 
   Reporter: Jeff French

    Created: Mon, 11 Aug 2003 11:28 PM
    Updated: Fri, 15 Aug 2003 4:57 AM
Environment: Mandrake Linux 7.2
JDK 1.4.0

Description:
I get an NPE when running Maven with the -d option to specify a
different effective working directory, but if I cd to the directory
and run the exact same command, it works. I tried with both b10 binaries and rc1stable from source. I blew away my plugins directory before each test.

Details
-------
When I run Maven this way:

  cd /tmp
  maven -e -X -d /tmp/work/subdir/projectA my:debug

I get:

java.lang.NullPointerException
        at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:416)
        at org.apache.maven.MavenSession.attainGoals(MavenSession.java:348)
        at org.apache.maven.cli.App.doMain(App.java:525)
        at org.apache.maven.cli.App.main(App.java:1088)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
        at java.lang.reflect.Method.invoke(Method.java:324)
        at com.werken.forehead.Forehead.run(Forehead.java:543)
        at com.werken.forehead.Forehead.main(Forehead.java:573)

But this works:

  cd /tmp/work/subdir/projectA
  maven -e -X -d /tmp/work/subdir/projectA my:debug

my:debug:
    [echo] 
      basedir=/tmp/work/subdir/projectA
      maven.home=/usr/local/maven/current
      maven.build.dir=/tmp/work/subdir/projectA/target
      maven.build.dest=/tmp/work/subdir/projectA/target/classes
      maven.test.dest=/tmp/work/subdir/projectA/target/test/classes
      user.dir=/tmp/work/subdir/projectA



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org