I wrote this one eons ago that is related:
http://jira.codehaus.org/browse/MNG-1974
-Original Message-
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
Sent: Tuesday, February 13, 2007 11:28 PM
To: Maven Developers List
Subject: Re: More control over what WARNING
On 14 Feb 07, at 4:41 AM 14 Feb 07, Barrie Treloar wrote:
There is no config file, we set the threshold programmatically. New
logger stuff in plexus will allow more domain like logging
configuration. But not in 2.0.x.
What logging system is used? Java Logging, Log4J, Apache?
(I haven't got ar
There is no config file, we set the threshold programmatically. New
logger stuff in plexus will allow more domain like logging
configuration. But not in 2.0.x.
What logging system is used? Java Logging, Log4J, Apache?
(I haven't got around to looking at the code yet)
Is there a way to specify t
+1 I am in favor of that too (see my previous comment).
Stéphane
On 2/14/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 13 Feb 07, at 8:40 PM 13 Feb 07, Jason Dillon wrote:
> Any comments from the Maven developers on this one?
>
Give me a one line sample of each type of message that's too v
I put some comments with examples of WARNING messages in this JIRA I
just created:
http://jira.codehaus.org/browse/MNG-2823
--jason
On Feb 13, 2007, at 5:53 PM, Jason van Zyl wrote:
On 13 Feb 07, at 8:40 PM 13 Feb 07, Jason Dillon wrote:
Any comments from the Maven developers on thi
On Feb 13, 2007, at 5:51 PM, Barrie Treloar wrote:
On 2/14/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
Any comments from the Maven developers on this one?
I really think all these WARNING messages are more harmful than
useful... running a build thats all I see when I glance at the
console. Th
On Feb 13, 2007, at 5:51 PM, Barrie Treloar wrote:
On 2/14/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
Any comments from the Maven developers on this one?
I really think all these WARNING messages are more harmful than
useful... running a build thats all I see when I glance at the
console. Th
On 13 Feb 07, at 10:01 PM 13 Feb 07, Barrie Treloar wrote:
On 2/14/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 13 Feb 07, at 8:40 PM 13 Feb 07, Jason Dillon wrote:
> Any comments from the Maven developers on this one?
>
Give me a one line sample of each type of message that's too verbos
On 2/14/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 13 Feb 07, at 8:40 PM 13 Feb 07, Jason Dillon wrote:
> Any comments from the Maven developers on this one?
>
Give me a one line sample of each type of message that's too verbose,
and I can see about flipping it to debug instead of info.
On 13 Feb 07, at 8:40 PM 13 Feb 07, Jason Dillon wrote:
Any comments from the Maven developers on this one?
Give me a one line sample of each type of message that's too verbose,
and I can see about flipping it to debug instead of info.
Jason.
I really think all these WARNING messages ar
On 2/14/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
Any comments from the Maven developers on this one?
I really think all these WARNING messages are more harmful than
useful... running a build thats all I see when I glance at the
console. They really make it much more harder than really needed
Any comments from the Maven developers on this one?
I really think all these WARNING messages are more harmful than
useful... running a build thats all I see when I glance at the
console. They really make it much more harder than really needed to
_see_ what is really going on.
That, and
My builds produce more than 1mo of logs, and like Jason, I used seldom
the warn msg. Thus, I am in favor of the -W flag.
Cheers,
Vincent
2007/2/12, Jason Dillon <[EMAIL PROTECTED]>:
I was imagining that a -W flag would actually internally set the log
level of what ever component was spitting t
I was imagining that a -W flag would actually internally set the log
level of what ever component was spitting those out.
--jason
On Feb 12, 2007, at 12:30 AM, Stephane Nicoll wrote:
Oh. I guess that another solution would be to lower the log level of
those messages instead. I mean it makes
Oh. I guess that another solution would be to lower the log level of
those messages instead. I mean it makes sense to see warning message
by default but maybe some messages are logged to this level
incorrectly.
Stéphane
On 2/12/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
+1 especially when y
+1 especially when you have 3 repositories declared in your pom and
the dependencies are on the last one :)
Cheers,
Stéphane
On 2/12/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
It would really be nice if there was more control over what WARNING
messages that Maven spits out by default. When
It would really be nice if there was more control over what WARNING
messages that Maven spits out by default. When building off of a
clean repo, a bunch of '[WARNING] Unable to get resource ...'
messages litter the console output... which really makes it hard to
see what is actually going
17 matches
Mail list logo
