You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?