[
https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugi...
]
Vsevolod Golovanov commented on JBIDE-20071:
--------------------------------------------
{quote}is there a reason why this was done separately from JBIDE-15250{quote}
As for me, I didn't touch the utility jars because as I noted in JBIDE-15250:
{quote}I don't know if there ever was a bug with exploded jars in ear/lib.
The fixed AS7-4704 is about exploded jars in wars specifically, and judging by the
stacktrace the fix was probably made at the WarStructureDeploymentProcessor.{quote}
So I made changes which were guaranteed to work according to AS7-4704.
Allow deploying exploded jars to war/WEB-INF/lib
------------------------------------------------
Key: JBIDE-20071
URL:
https://issues.jboss.org/browse/JBIDE-20071
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.2.3.Final
Environment: JBoss Developer Studio 8.1.0.GA
Reporter: Vsevolod Golovanov
Assignee: Rob Stryker
Labels: new_and_noteworthy
Fix For: 4.3.0.Beta2
There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying
expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason
seemed to be that the server at the time refused to deploy such structure. Maybe the
server was in the wrong? This was fixed in AS7-4704.
Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least
Weld, EJB, JSF seem to work fine.
The main use case for this is creating a modular web application, with different parts
implemented in separate projects. Hot deploying of resources, such as Facelets'
XHTMLs, is crucial for development. So the JARs need to be exploded.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)