hi shade can possibly juxtapose jar deps diffrently from one build to the next in my experience. if you think you are having collisions you should probably do 2 things
1) use <exclude> on the older jar from the older <dependency> to avoid the collision 2) see if proguard fixes what shade breaks, if shade stays broken after #1. it's pretty intense On Mon, Jul 7, 2014 at 12:21 PM, Robert James <[email protected]> wrote: > I have a jar that I need to shade - that is, change the name of many > of the internal classes (to avoid conflicts with another jar) except > for a few classes which remain exposed. The jar is already built, > source is not at hand. How can I use maven shade to shade that jar? > > (Disclaimer: I'm a maven neophyte) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Jim Northrup * (408) 837-2270 *
