Does anyone have more information about this: HipChat Core 0.6 includes a bunch of google, apache and codehaus classes that break other plugins?
There is a reference to: Plugin disabling - Constraint violation for package 'com.google.common.base', and therefore we updated our HipChat version 1.2.5 (pre-installed with JIRA 6.1.5 but with an older HipChat Core Plugin), to the latest version.
If HipChat could be a risk regarding system stability, does it make sense to disable it, if we are not using it?
Also - btw - as general best practice and fyi: ANY plugin can on occassion have an incompatibility like this. These scenarios are more and more rare these days than years ago - but they can happen. Best practices sys admining of running staging systems to test plugins (by ANY vendor!) is a good idea. In this case, being bundled, it just kinda got caught - but also why was fixed quickly.
...from the beginning. We have built up a lot of content in HipChat, with it being a core tool in our distributed company model. While it is true that we didn’t need to move to Slack immediately, we felt it...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs