[
https://jira.codehaus.org/browse/MSHADE-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272205#comment-272205
]
Robert Burrell Donkin commented on MSHADE-8:
--------------------------------------------
IMHO debugging shade is distinct issue from verification rules for the
completed build. Typically, better instrumentation with logging is a better
solution to debugging problems than adding extra rules that may catch people
expecting otherwise. But it's quite reasonable to want to verify that no
original class has been relocated.
Been thinking that it might be useful to track the origins of resources. This
would allow (for example) generation of accurate licensing information. This
would also allow application of verification rules...
> Shade plugin will cheerfully relocate your own classes
> ------------------------------------------------------
>
> Key: MSHADE-8
> URL: https://jira.codehaus.org/browse/MSHADE-8
> Project: Maven 2.x Shade Plugin
> Issue Type: Improvement
> Affects Versions: 1.0-alpha-15
> Reporter: Dan Fabulich
>
> My relocation patterns were initially too relaxed, and so they wound up
> relocating my own classes, rather than just the classes I depend on.
> I could imagine somebody wanting to do this, but I think there should
> probably be a safety check or something to try to help you not do it by
> accident; it's probably not what you want. (After all, if you wanted your
> code to be in a different package, wouldn't you have just written it that way
> to begin with?)
> In my case I was working on a Maven plugin; when its classes got relocated,
> it broke the plugin metadata... definitely not what I wanted.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
