[EMAIL PROTECTED] 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
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
+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)
[EMAIL PROTECTED] wrote:
In an effort to get a consistent way of pro
Brett Porter <[EMAIL PROTECTED]> wrote on 08/08/2003 05:17:21 PM:
> My non-committer +1
>
> This would allow most of what I proposed in:
> http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-553
> Via a log4j configuration file.
>
> 3 questions:
> 1) where does this leave maven.log? Just pl
[EMAIL PROTECTED] writes:
use commons-logging and let the user decide via environment. Default
to log4j.
Regards
Henning
>--=_alternative 0029A21DCA256D7C_=
>Content-Type: text/plain; charset="US-ASCII"
>Brett Porter <[EMAIL PROTECTED]> wrote on 08/08/2003 05:17:21 PM:
Can you tell me how to change the debug level at run time under program
control.
I can't see how this is possible using commons-logging (would love to be
wrong though).
Until that's possible, I can't see how we can truly support a '-debug'
flag.
Can you?
--
dIon Gillard, Multitask Consulting
nt: Monday, 11 August 2003 5:23 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Console output from Maven - consistency
>
>
> [EMAIL PROTECTED] writes:
>
> >Until that's possible, I can't see how we can truly support
> a '-debug'
> >flag.
>
>
[EMAIL PROTECTED] writes:
>Until that's possible, I can't see how we can truly support a '-debug'
>flag.
>Can you?
Well, I'd simply change the level that is reported to the console. If
-debug is not set, don't report anything below "warn" level to the
console. So the application keeps logging
+1
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 08 August 2003 09:12
> To: [EMAIL PROTECTED]
> Subject: Console output from Maven - consistency
>
> In an effort to get a consistent way of producing console output from
> Maven,
ubject: 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 th
> > 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
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
[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
ab
13 matches
Mail list logo
