"Jar Hell" in Eclipse project that requires JBoss modules jars


(Tim Bessie) #1

I'm having a problem similar to Trivial NodeBuilder Java code resulting in "jar hell" error

... except that I'm getting conflicts between jars loaded from the eclipse project libraries and libraries in our Jboss server installation. We have code that accomplishes various "tasks", but running standalone in a faked-up server environment (we load the Jboss libraries, and hand-create sessions, etc. for database connectivity, etc. This is all run from within Eclipse.

No other library we're using complains about the classpath, but Elasticsearch 2.2 does. Is there any way we can tell Elasticsearch not to be so picky about the classpath, but just take the first found class it's looking for?

  • Tim

Elasticsearch jar hell when writing integration tests
(Tim Bessie) #2

Anyone?

  • Tim

(system) #3