[
http://jira.codehaus.org/browse/MSHADE-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Fabulich updated MSHADE-8:
------------------------------
Description:
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.
was:
My relocation patterns were initially too relaxed, and so they wound up shading
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 shaded, it
broke the plugin metadata... definitely not what I wanted.
Summary: Shade plugin will cheerfully relocate your own classes (was:
Shade plugin will cheerfully shade your own classes)
> Shade plugin will cheerfully relocate your own classes
> ------------------------------------------------------
>
> Key: MSHADE-8
> URL: http://jira.codehaus.org/browse/MSHADE-8
> Project: Maven 2.x Shade Plugin
> Issue Type: Improvement
> 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.
-
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
