[
https://issues.jboss.org/browse/JBIDE-15250?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-15250.
---------------------------------
Resolution: Done
Rob Stryker, how do I control whether the included jar project is
exploded or zipped? Or is it either all exploded or all zipped including the ear?
You cannot control it. It is based on what the server adapter itself supports. If we find
that the server adapter itself supports something other than we implement, than we change
the code. I'm sure that's not exactly satisifying to you, since it doesn't
exactly provide you an easy way to override and test to see if our impl differs from
reality :(
Explode utility jars in EAR/WAR deployments
-------------------------------------------
Key: JBIDE-15250
URL:
https://issues.jboss.org/browse/JBIDE-15250
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.0.1.Final
Reporter: Kevin Formsma
Assignee: Rob Stryker
Labels: respin-a
Fix For: 4.3.0.Beta2
Attachments: test-ear.zip
For larger projects that utilize utility jars within the EAR, it would be nice to have
these deployed exploded as well. This would allow hot code replacement for those utility
projects.
A current work around is to make the utility projects modules so that the tooling treats
them as a EJB module and deploys them exploded.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)