[
https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-17700:
-------------------------------------
To be clear, I still haven't replicated the issue, so I don't know if these will
work. But, it seems to be the most logical workaround I can think of. We should ensure
that these classes are loaded earlier, perhaps before m2e (or others?) had a chance to
mess with the classloaders. It's possible it works. Max has approved it in
principle, but I'll keep working to replicate
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: forge, maven, server
Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place)
Reporter: Oliver Pfau
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.2.0.Beta3
Attachments: jbosstools-diagnostics-20140707141907.zip, pom.xml
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)