[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-17700: ------------------------------------- Aparently a bug in the platform? https://bugs.eclipse.org/bugs/show_bug.cgi?id=396554#c6 : After some additional research, it would appear that we are running into an inherent limitation in the ContextFinder in Equinox (and perhaps more accurately stated as a limitation of the Java VM/TCCL and OSGi). The classloader that initially loads the Velocity class is being cached (since Velocity uses Class.forName(...) to load the class), and subsequently reused outside of the scope of the m2e bundle that loaded it. As a result, when Dali or any other Velocity user comes along and tries to initialize Velocity, it will fail, as the ContextFinder will use the initially cached classloader to load the class, resulting in the failure of Velocity to initialize. See the following links for more information: http://blog.bjhargrave.com/2007/07/contextfinder-in-eclipse-is-broken.html https://bugs.eclipse.org/bugs/show_bug.cgi?id=127963 https://bugs.eclipse.org/bugs/show_bug.cgi?id=127963#c22 (this comment is key) {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)