]
Max Rydahl Andersen commented on JBIDE-20071:
---------------------------------------------
[~nogotiated] please open bug describing your setup. We should most definitely not see
performance go 3x slower for this.
[~rob.stryker] sounds like we need to have this "agressive exploded jars" be
something to optional turn on (or off) ? are we at least not exploding bundled jars and
only exploding users modules ?
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.