[ https://issues.jboss.org/browse/JBIDE-15250?page=com.atlassian.jira.plugi... ] Christian Beikov edited comment on JBIDE-15250 at 12/31/14 11:46 AM: --------------------------------------------------------------------- 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). The contents of the file can be viewed by browsing to localhost:8080/test-war/index.xhtml was (Author: christian.beikov): 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). -- This message was sent by Atlassian JIRA (v6.3.11#6341)