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. Has anyone else seen this? I
looked in Jira, but didn't see a report on it. I seem to remember
reading someplace that Java has a problem figuring out the CWD. Could
that be it?
This is on Mandrake Linux 7.2. I tried both beta10 from binaries and
rc1stable built from source. I blew away my plugins directory before
each test.
Details
-------
When I run Maven as:
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)
Total time: 8 seconds
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
BUILD SUCCESSFUL
Total time: 10 seconds
Jeff
--
mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
