maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Taylor Jones (JIRA)" <j...@codehaus.org>
Subject [jira] (MSHADE-176) Suppress warning output
Date Fri, 01 Aug 2014 03:11:10 GMT
Taylor Jones created MSHADE-176:
-----------------------------------

             Summary: Suppress warning output
                 Key: MSHADE-176
                 URL: https://jira.codehaus.org/browse/MSHADE-176
             Project: Maven Shade Plugin
          Issue Type: Improvement
            Reporter: Taylor Jones
         Attachments: suppressWarnings_option.patch

The warnings Shade outputs are useful, but there are some cases where nothing can actually
be done about them. Recently, I encountered this with the Neo4j libraries; there is one overlapping
class between two critical JARs (kernel and rest), and no way to resolve this via exclusions.


In these cases, everything works just fine. At best, the warnings are just noise, but we also
have some build processes in place that will fail on Maven warnings. I figured this would
be a pretty simple thing to just suppress, but Shade doesn't seem to have a way to do this.

I've included a simple patchset to address.this which adds a new option to the configuration
called `<suppressWarnings>`. There isn't a unit test attached, unfortunately. I'm not
quite sure how to unit test logging output in this fashion without something akin to Mockito.
I figured you guys wouldn't appreciate me adding dependencies out of the blue but if a unit
test is required, I can give it a shot.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message