[
https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-17700:
-------------------------------------
I actually can't think of *ANY* reason at all why any thread running in eclipse would
have org.codehaus.plexus.classworlds.realm.ClassRealm as its class loader. It would seem
to me that eclipse, as an osgi-container basically, should be in charge of the
classloaders entirely.
I did a grep on my installation's "plugins" folder, and the only plugins
that seem to mention org.codehaus.plexus.classworlds is
org.eclipse.m2e.maven.runtime_1.5.0.20140505-1310
Is m2e behaving badly here? Is it setting its classloader and not putting it back?
Cannot deploy jsf war with eclipse luna and jboss 7.1.x
-------------------------------------------------------
Key: JBIDE-17700
URL:
https://issues.jboss.org/browse/JBIDE-17700
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place)
Reporter: Oliver Pfau
Priority: Critical
When I publish my war to jboss 7.1 the following error occurs:
An internal error occurred during: "Publishing to JBoss AS 7.1...".
Could not initialize class de.schlichtherle.io.ArchiveControllers
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)