Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/2498
@arunmahadevan
I think we are all on the same page here. All I am saying is that this
patch by itself does not fix STORM-2881 for 2.x and as such I don't want it to
go in as is, we need to come up with a full fix. The 1.x patch looks good to
me and in this case I would be fine with merging it in without a full 2.x fix.
The choices I see to fix 2.x are
1) shade curator in storm-client,
2) shade curator in storm-druid, or
3) we change tranquility to use an up to date version of curator.
Shading has lots of problems. Newer versions of maven don't support it
properly and it makes development with an IDE a real pain because the IDE does
not know about it. These are the reasons that we wanted to go away from using
it, but I think getting working code trumps all of them. If you do want to do
shading again, I think I have some ideas that might mitigate some of the IDE
issues, but I personally think that choice 2 is the best long term fix.
---
