You can make the commons-lang version 2.3 in xwiki-core pom.xml Thanks Sachin vmassol wrote:
On Mar 21, 2008, at 8:01 AM, Sachin Mittal wrote:
Hi, I have frequently encountered this problem that versions of third party jars across modules are not uniform. Like the xwiki-core uses commons-lang of version 2.1 and lucene 2.3. Similarly some module uses xerces-impl of version 2.0.2 where as some other 2.8.1.
As the xwiki build can be made of different modules as per custom requirements, when we bring these modules together there is a conflict in the jar versions.
This way different jars of same version end up in the lib directory and causes class not found exceptions.
I don't know what is the best way to avoid such a problem, but best I can think is when building the pom we should ensure that version of the third party jar stays uniform atleast across xwiki-platform.
Yes you're right.
The solution is to use dependencyManagement in Maven in the top level POM. The way to find the different version is to run the convergence report.
Please feel free to submit patches.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
----- http://www.assembla.com/wiki/show/sachin_mittal about me: -- View this message in context: http://www.nabble.com/Keeping-uniform-jar-versions-across-modules-tp16194595... Sent from the XWiki- Dev mailing list archive at Nabble.com.