Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/1800
So shading is not really an option for jersey.
I was able to split the DRPC server off into its own package with tests,
but packaging it up with the assembly plugin is proving to be difficult. If I
upgrade to 3.0.0 of the assembly plugin I can use moduleSets and make it work,
but I have to change {{storm-dist/binary}} to a multi-module build and move the
code that actually packages the final release to a sub package under it. Oh
and we leak two empty/useless jar files into the release package that should be
ignored. moduleSets do not package pom modules. They require an artifact that
is a file.
I really dislike all of these options. I see a few cleaner options, but
they will require a lot more work.
1. Move to gradle
2. Change how we do shading so that the assembly subModule code works the
way they intended it.
This would involve essentially having a separate package/build for what
we want shaded (i.e. storm-shaded-deps.jar)
If someone has a cleaner solution I am happy to do it, but I think option 2
is the best so far, although I don't like it all that much.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
