Hi Henning, "Henning P. Schmiedehausen" <[EMAIL PROTECTED]> wrote on 08/08/2003 08:52:27 PM:
> [EMAIL PROTECTED] writes: > > >1 - commons logging 'info' level output from all org.apache.maven.* > >classes is to go to the console. > >2 - the '-debug' option should set the log4j default level to debug for > >org.apache.maven.* > > +1 > > You might also look into things like this (from b9-dev, don't know > about the current code, but I'm pretty sure that it's still in there). > > % cd /tmp (or any other directory without any maven related stuff) > % maven > java.lang.NullPointerException > at org.apache.maven.plugin.PluginManager. [snip] I'm sure that got fixed. Will see if I can recreate it now. C:\Temp>maven __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT BUILD FAILED No goal specified and no project.xml found. Total time: 1 seconds Finished at: Mon Aug 11 10:24:09 EST 2003 C:\Temp>dir project.xml Volume in drive C has no label. Volume Serial Number is 1CC6-E2C6 Directory of C:\Temp File Not Found > Dropping a "maven.log" file everywhere in the current working > directory isn't too nice, either. Send output to the console or make > it writeable to a file with e.g. -f maven.log. Raise this one as a report in Jira. Where would you prefer the output go, most of it's debugging stuff. The console doesn't make much sense. The -f option sounds ok, or --log? -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/
