HipChat incompatibility with other plugins

[Jose M.]

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?

[Boris Berenberg · Accepted solution]

Disabling it should not cause any problems for your system. However, if you are on a modern version of the plugin, this problem has already been fixed and will not affect you.

[Jose M.]

Thanks for the answer. Do you know, why the issue is still in status New: https://bitbucket.org/atlassian/hipchat-for-jira/issue/9/hipchat-core-06-includes-a-bunch-of-google

[Boris Berenberg]

That site is not the actively used bug tracker for the issue. The one it links to in jira.atlassian.com is where the issue was tracked and worked. The user was just submitting it elsewhere to try and improve visibility into the issue I believe.

[Ellen Feaheny [AppFusions]]

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.