Hi, Could you enumerate which projects don't catch up the change of Apache Storm 1.0.0+? I think we need to get in touch and let them follow up (or we could help) recent change.
Thanks, Jungtaek Lim (HeartSaVioR) 2016년 8월 26일 (금) 오후 5:36, Abhishek Agarwal <[email protected]>님이 작성: > In your pom, you can add class relocation ( > > https://maven.apache.org/plugins/maven-shade-plugin/examples/class-relocation.html > ) > > You can add the patterns in this class - > > https://github.com/apache/storm/blob/master/storm-rename-hack/src/main/java/org/apache/storm/hack/StormShadeRequest.java > > > > > On Fri, Aug 26, 2016 at 1:28 AM, S G <[email protected]> wrote: > > > Hi, > > > > Our project is planning to upgrade storm from 0.10.0 to 1.0.2 > > We use a couple of 3rd party storm dependencies like storm-jms, > > https://github.com/HolmesNL/kafka-spout etc. > > > > Some of these projects have plans to upgrade soon to 1.0.2 but some do > not > > have it on their roadmap. > > > > What is the best strategy to proceed in such a case? > > > > I do not want to copy-and-maintain all the 3rd parties code myself. > > > > Is there a maven-trick published somewhere to do this? > > > > Thanks > > SG > > > > > > -- > Regards, > Abhishek Agarwal >
