You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by di...@multitask.com.au on 2003/08/08 09:12:06 UTC
Console output from Maven - consistency
In an effort to get a consistent way of producing console output from
Maven, I'd like to propose the following:
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.*
Comments/votes?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Re: Console output from Maven - consistency
Posted by di...@multitask.com.au.
Hi Henning,
"Henning P. Schmiedehausen" <hp...@intermeta.de> wrote on 08/08/2003
08:52:27 PM:
> dion@multitask.com.au 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/
Re: Console output from Maven - consistency
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
dion@multitask.com.au 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.attainGoals(PluginManager.java:362)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
at org.apache.maven.cli.App.doMain(App.java:524)
at org.apache.maven.cli.App.main(App.java:1080)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
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: 1 seconds
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.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
"You are being far too rational for this discussion."
--- Scott Robert Ladd in <3F...@coyotegulch.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Console output from Maven - consistency
Posted by Peter Lynch <pe...@mindspring.com>.
dion@multitask.com.au wrote:
> In an effort to get a consistent way of producing console output from
> Maven, I'd like to propose the following:
>
> 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.*
>
> Comments/votes?
> --
> dIon Gillard, Multitask Consulting
> Blog: http://blogs.codehaus.org/people/dion/
>
Sounds good. +1
-Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Console output from Maven - consistency
Posted by Ben Walding <be...@walding.com>.
+1
Once I work out where I have to commit to I'll go and search and destroy
any dodgy logging methods I've been using (I use System.out in the
linkcheck because it was the only thing I could get to work when I was
tinkering)
dion@multitask.com.au wrote:
>In an effort to get a consistent way of producing console output from
>Maven, I'd like to propose the following:
>
>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.*
>
>Comments/votes?
>--
>dIon Gillard, Multitask Consulting
>Blog: http://blogs.codehaus.org/people/dion/
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Console output from Maven - consistency
Posted by Vincent Massol <vm...@pivolis.com>.
+1
> -----Original Message-----
> From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> Sent: 08 August 2003 09:12
> To: dev@maven.apache.org
> Subject: Console output from Maven - consistency
>
> In an effort to get a consistent way of producing console output from
> Maven, I'd like to propose the following:
>
> 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.*
>
> Comments/votes?
> --
> dIon Gillard, Multitask Consulting
> Blog: http://blogs.codehaus.org/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org