Upgrade third party libraries (provided by confluence) in custom plugins

Shanker P

In confluence 6.6.3 server WEB_INF/lib, guava 18.0 jar is provided.

So I have added guava 18.0 in maven dependencies (scope as provided) of custom plugin.

Now to fix one vulnerability in guava 18.0, I want to upgrade it to Guava 25.0.

So if I use Guava 25.0 in maven dependency (scope as compile), will that be okay?

Would there be any conflicts, because Guava 18.0 is already provided by confluence?

 

Thanks,

Shanker.

Shanker P

Incase anyone come across the issue...

I have tried to add the latest version of Guava in dependencies.

But confluence is throwing errors when tried to upload the plugin. So I think, it is not possible to upgrade the dependency provided by confluence.