[ https://issues.jboss.org/browse/JBIDE-13405?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13405: ------------------------------------- I found the error. There's a single-use protected method in the publishers that returns an incorrect value for the case of child modules. The method is getParentDeployPath(IModule[] moduleTree, IDeployableServer server); The error here is that this method should be returning the module's deploy root's PARENT, for example, given a web (MyWeb.war) with a nested utility project (MyUtil.jar) with relative path "WEB-INF/lib", This method should be returning {rootDeployDir}/MyWeb.war/WEB-INF/lib, but is actually returning {rootDeployDir}/MyWeb.war/WEB-INF/lib/MyUtil.jar This method is only called during child projects that are to be published zipped (like utility jars, java projects, etc). The effect this has is that the file-transfer util is instantiated with a root directory, and each file in that module is transferred relative to the root its instantiated with. This transfer util is being instantiated with {rootDeployDir}/MyWeb.war/WEB-INF/lib/MyUtil.jar. The utility is then being asked to move the zipped jar file to relative path "". This is obviously wrong. It should be instantiated with {rootDeployDir}/MyWeb.war/WEB-INF/lib/ and the relative path for the zip should be "MyUtil.jar". The local copy utility is able to handle this error. The RSE handler is not capable of handling this. The fix is to either fix the method to return the correct value, or ensure that RSE can also work around it. Obviously, the first solution is correct. PR: https://github.com/jbosstools/jbosstools-server/pull/174 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira