[jbosstools-issues] [JBoss JIRA] (JBIDE-20577) Allow setting exploded or zipped on per-module basis

[ https://issues.jboss.org/browse/JBIDE-20577?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20577: ------------------------------------- Your language here is pretty unclear. There are several interpretations: 1) A global on/off switch for each deployment (read project) sounds like you're suggesting a configuration setting in the project itself to declare whether it should be zipped or not. This isn't something I'd really support, because it takes control out of the server adapter's hands, but also because a user may wish to always deploy exploded to (server1) where they test things intricately, and to deploy zipped to (server2) where they do integration testing and make no changes on the fly. 2) It could be interpreted that you mean a global on/off switch on a per-module-TYPE basis. ie, always zip nested utilities, but never zip nested war projects. Again, if this was global, it could conflict with some people's workflows, who may use one server to dev against and another for integration testing. So ideally it would still be set on the server rather than globally, so users can customize it per-server. 3) But even then, there will be users who *usually* want a war exploded, but don't want THIS war exploded ever, for whatever reason. So basically, I'm not sure exactly what you mean, but the few interpretations I can think of don't seem suitable? It still seems like users will want a per-server-type customization, and, even then, other users will want to split up behavior for two different web projects, making one zipped and one unzipped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)