[ 
http://jira.codehaus.org/browse/MNG-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87523
 ] 

Jason Dillon commented on MNG-2823:
-----------------------------------

The biggest offender I know of is:

{noformat}
Downloading: 
http://ws.zones.apache.org/repository2//org/apache/geronimo/genesis/config/project-config/1.1/project-config-1.1.pom
[WARNING] Unable to get resource 
'org.apache.geronimo.genesis.config:project-config:pom:1.1' from repository 
axis2-m2-repo (http://ws.zones.apache.org/repository2/)
{noformat}

I put the "Downloading: ..." line in here too, since they seem to go hand in 
hand.  Would be nice to *only* show "Downloading: ..." when its actually there 
to download, else log a DEBUG about "Attempting to download: ..."

This one does not show up much, but more often than not its not a problem:

{noformat}
[WARNING] Unable to load parent project from repository: Could not find the 
model file '/Users/jason/ws/geronimo/server/../pom.xml'.
{noformat}

This is a lame duck warning (should not log this, since the expected prefix 
matches what's there)

{noformat}
[WARNING] Goal prefix is: geronimo; Maven currently expects it to be geronimo
{noformat}

Some places the ^^^ warning actually shows a problem, though with all the 
"Unable to get resource" I tend to miss them.

And then a few of these:

{noformat}
[WARNING]
    Artifact org.apache.xbean:xbean-finder:jar:2.8:runtime retains local scope 
'runtime' overriding broader scope 'compile' 
    given by a dependency. If this is not intended, modify or remove the local 
scope.
{noformat}

I've yet to run into a situation where I wanted to change the scope based on 
this message, usually the scope was correct.  So its a little bit more noise to 
sort though.

But, the biggest one is the first... I have ~2k of these messages in a Geronimo 
server build.  If nothing else I'd like to see that log become a DEBUG message. 
 And the WARNING about the plugin prefix should be removed unless the prefix 
configured doesn't actually match what is expected.


> More control over what WARNING messages are displayed
> -----------------------------------------------------
>
>                 Key: MNG-2823
>                 URL: http://jira.codehaus.org/browse/MNG-2823
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Logging
>    Affects Versions: 2.0.4
>            Reporter: Jason Dillon
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to