You should set a break point and inspect the call stack that leads to the ServiceLoader call. Maybe you have two different loaded versions of ServiceLoader?

Am 22.04.2015 08:26, schrieb Johannes Hoffart:
Jan,

thanks for your response. This was also my first intuition, but I don't think 
that I have conflicting versions here. I pasted the output of mvn 
dependency:tree here: http://pastebin.com/jtaQejjR

I investigated further by putting a breakpoint in ServiceLoader.nextService():

The class org.eclipse.jetty.apache.jsp.JuliLog is tried for loading two times. 
The first time it works fine, the second time the Error below is thrown. The 
ClassLoader seems to be the same as well. I could not find any other maven 
dependency that in the end boils down to  org.eclipse.jetty.apache.jsp.JuliLog, 
so I don't understand why it is loaded twice. Is there an easy way to figure 
out which maven dependency actually causes the loading of this class?

Cheers
Johannes

_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to