https://answers.axonivy.com/questions/1762/why-there-are-two-guava-jars-in-axon-ivy-engine-s-lib-shared<p>Hi Ivy team</p> <p>Our team are about to use Guava in our project. The version we use is 19.0. When we test on Axon.ivy Designer, everything works just fine. However, when we deploy on engine, it get exception at runtime:</p> <p><code>Caused by: java.lang.NoSuchMethodError: com.google.common.collect.Range.closed(Ljava/lang/Comparable;Ljava/lang/Comparable;)Lcom/google/common/collect/Range;</code></p> <p>After digging around, we discovered that there are 2 jars of guava in Axon.ivy engine's <code>lib/shared</code> directory: <code>guava-16.0.1.jar</code> and <code>guava-11.0.2.jar</code>. At runtime, somehow Axon.ivy Engine chooses to load <code>guava-11.0.2.jar</code> and ignore the other jar.</p> <p>My questions are:</p> <ul> <li>Why there two jars of two different version?</li> <li>Is there anyway we can use <code>guava-19.0</code> without overriding Axon.ivy engine's <code>lib/shared</code>?</li> </ul>enTue, 10 May 2016 14:51:39 -0400https://answers.axonivy.com/questions/1762/why-there-are-two-guava-jars-in-axon-ivy-engine-s-lib-shared#1767<p>No its not intentional. I've fixed it on trunk. With the next version (6.2) only guava-16 will be on the classpath.</p>Reguel WermelingerTue, 10 May 2016 14:51:39 -0400https://answers.axonivy.com/questions/1762/why-there-are-two-guava-jars-in-axon-ivy-engine-s-lib-shared#1767https://answers.axonivy.com/questions/1762/why-there-are-two-guava-jars-in-axon-ivy-engine-s-lib-shared#1766<p>But you haven't answered the first question though: why are there 2 version of guava in axon.ivy engine's shared lib? Is it intentional?</p>Genzer HawkerTue, 10 May 2016 14:44:36 -0400https://answers.axonivy.com/questions/1762/why-there-are-two-guava-jars-in-axon-ivy-engine-s-lib-shared#1766https://answers.axonivy.com/questions/1762/why-there-are-two-guava-jars-in-axon-ivy-engine-s-lib-shared#1765<p>It could be part of the 'applicationContextVersion' feature which we are prototyping right now and should be released at least with 7.0. But to be 100% sure, that the server runtime behaves like the designer, OSGI classloading is required. Today there are no plans to do this...</p>Reguel WermelingerTue, 10 May 2016 13:59:40 -0400https://answers.axonivy.com/questions/1762/why-there-are-two-guava-jars-in-axon-ivy-engine-s-lib-shared#1765https://answers.axonivy.com/questions/1762/why-there-are-two-guava-jars-in-axon-ivy-engine-s-lib-shared#1764<p>Then somehow I lose the benefits of using <code>maven</code> to control dependency. Not to mention I have to re-repack every time I want to use a newer version. Is there any better way to deal with this? I mean, in the future release of Axon.ivy?</p>Genzer HawkerTue, 10 May 2016 13:36:55 -0400https://answers.axonivy.com/questions/1762/why-there-are-two-guava-jars-in-axon-ivy-engine-s-lib-shared#1764https://answers.axonivy.com/questions/1762/why-there-are-two-guava-jars-in-axon-ivy-engine-s-lib-shared/1763<p>I suggest that you repackage the guava version you want to use into a new namespace. Then you are save that no other version is used. More about repackaging can be found in this post: <a href="http://answers.axonivy.com/questions/960/use-the-latest-hsqldb-within-my-project">http://answers.axonivy.com/questions/960/use-the-latest-hsqldb-within-my-project</a></p>Reguel WermelingerTue, 10 May 2016 13:27:57 -0400https://answers.axonivy.com/questions/1762/why-there-are-two-guava-jars-in-axon-ivy-engine-s-lib-shared/1763