[
http://jira.codehaus.org/browse/MSHADE-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247775#action_247775
]
Andrew Swan commented on MSHADE-91:
-----------------------------------
One workaround would be to use a custom Shader implementation; is this
possible? The Shader field in the ShaderMojo is declared thus:
{code:title=Shader.java}/**
* @component
* @required
* @readonly
*/
private Shader shader;{code}
>From what little I know about Plexus, this seems to indicate that the Shader
>is not pluggable?
> Allow failing of build if overlapping classes are detected
> ----------------------------------------------------------
>
> Key: MSHADE-91
> URL: http://jira.codehaus.org/browse/MSHADE-91
> Project: Maven 2.x Shade Plugin
> Issue Type: New Feature
> Affects Versions: 1.4
> Environment: N/A
> Reporter: Andrew Swan
>
> Currently if multiple shaded artifacts contain the same fully-qualified class
> name, the plugin issues a warning on the console like this:
> {code}[WARNING] We have a duplicate foo.bar.Baz.class in
> <path-to-jar-in-local-repo>{code}
> In many cases such duplicates are a serious problem, e.g. when they are not
> the same version of that class.
> It would therefore be useful if the plugin (specifically the DefaultShader
> class) provided the option of failing the build if any duplicates are
> detected. This would be particularly useful in a continuous integration
> environment where there's no human operator to check the console output for
> warnings.
--
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
