+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 verbose, and I can see about flipping it to debug instead of info. Jason. > 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 if you need to add a few more repos to pick up artifacts, > the output of mvn due to all of these WARNING messages increases > significantly. Logs end up as 80% WARNING, 20% actual build > related output. > > :-( > > --jason > > > On Feb 12, 2007, at 12:45 AM, Jason Dillon wrote: > >> 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 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 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 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 on. >>>> > >>>> > I'd like mvn to not show those by default, and have a flag to >>>> enable >>>> > them if needed... kinda like the -W flag on gcc. >>>> > >>>> > IMO these WARNING messages are only useful about 5% of the >>>> time when >>>> > strange dependency problems pop up... it would be better IMO >>>> if for >>>> > the remaining 95% that mvn didn't complain so much about stuff >>>> that >>>> > is not really a problem. >>>> > >>>> > --jason >>>> > >>>> > >>>> ------------------------------------------------------------------- >>>> -- >>>> > To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> > For additional commands, e-mail: [EMAIL PROTECTED] >>>> > >>>> > >>>> >>> >>> -------------------------------------------------------------------- >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
