These Apache developers work with Jira based on objective materials attached to Jira, like a reproducible project provided by you on Github or a provided POM. Then they will take care especially regarding the maven-shade-plugin they want to improve this plugin, and there was a big effort given to this plugin last time, so I am sure they want to handle the bugs in Jira again. T
On Sun, May 16, 2021 at 4:41 AM Alexander Kriegisch < [email protected]> wrote: > When running Maven Shade with relocation, it works nicely. When > comparing JARs before and after relocation, I was surprised to see that > Shade not just modifies the relocated classes and classes referencing > them, but also a bunch of IMO completely unrelated classes. In my case I > am transforming an uber JAR containing ASM, and I selectively relocate > the ASM classes, intending to leave all others untouched. I know that > ASM classes are referred to by some of the other classes, but by no > means as many as are being modified. The byte code is slightly > different, probably still does the same thing, but it makes comparisons > and sanity checks or automatic verification steps harder than necessary. > BTW, the same Shade execution also relocates the sources and really only > changes source files referencing ASM, just like I would have expected. > > Looking forward to your insights > -- > Alexander Kriegisch > https://scrum-master.de > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
