[kepler-users] Kepler 2.0, intermodular libraries conflict

Tomasz Żok tzok at man.poznan.pl
Fri Aug 6 07:11:24 PDT 2010


Hi,

I am developing a new module which uses several external .jar libraries.  
These are mostly well known and widely used libraries like log4j, etc.  
However I found out that there is a conflict in library versions that  
disables my module totally. I pinpointed the issue to the minimal subset  
of conflicting jars:
actors/lib/jar/commons-httpclient-3.0.1.jar
common/lib/jar/log4j-1.2.8.jar
common/lib/jar/sms/xercesImpl.jar

My module uses:
commons-httpclient-3.1.jar
log4j-1.2.16.jar
xercesImpl-2.7.1.jar

My libraries are in the classpath when I run Kepler, but they are not  
loaded, because the three conflicting ones precede them. What should I do  
in such situation? Should I somehow formally ask Kepler devs to update  
theirs or should I do anything with my libraries?

Best regards,
Tomek


-- 
Tomasz Zok
Poznan Supercomputing and Networking Center
ul. Noskowskiego 10, 61-704 Poznan, POLAND
http://www.man.poznan.pl



More information about the Kepler-users mailing list