I am developing a bamboo plugin which uses a third party library. This library in turn depends on N number of other libraries like javax.ws.*, jersey 2.x etc. Few of which dependencies are already part of the atlassian framework but have different versions and as a result there are some conflict issues. How can I force atlassian to use libraries provided by my plugin and not its internal system libraries?
There are ways to do it, but you should not. Unless you've checked that the Atlassian application is using compatible calls in every case, you don't want to pull the rug out from their code.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nic, Can you please mention those ways in which we can achieve overriding our library over atlassian if at all we need to do.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can't ever support you doing this as it can (and usually does) break the core application. Please, work with the core libraries.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.