[
https://issues.jboss.org/browse/JBIDE-15250?page=com.atlassian.jira.plugi...
]
Christian Beikov updated JBIDE-15250:
-------------------------------------
Attachment: test-ear.zip
Here I provide 3 example projects
* test-ear-with-lib - contains the problematic case which shows that a library jar is
deployed in zipped format
* test-ear-with-module - contains the described case which deploys the library jar as
utility module(DOES NOT WORK)
* test-ear-with-ejb - contains the only working solution which deploys the jar as ejb
module in the exploded form
It's always the same code. You can test it by starting the application from within
eclipse on a wildfly that runs in debug mode. Changes made to test-file.properties located
in jar/src/main/resources are only immediately visible, if deployed in the exploded
form(ejb module).
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
Fix For: 4.2.x
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.11#6341)