Github user srdo commented on the issue:
https://github.com/apache/storm/pull/2698
@revans2 If I'm understanding the problem correctly, the bug is that if
shaded-deps is in the same reactor as the other modules, Maven will read the
"normal" pom, rather than the dependency reduced pom, and put all the
shaded-deps dependencies onto the classpath of the other modules?
Would it work to make all the dependencies declared in shaded-deps optional
(i.e. non-transitive)?---
