[ https://issues.jboss.org/browse/JBIDE-21637?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21637: ------------------------------------- I'm sorry but I simply disagree. This shouldn't work as you're expecting it to. The deploy-only server is intended to be 100% agnostic of individual app-server behaviors. No other app-servers require a .dodeploy marker, and so that simply isn't part of the logic. Similarly, the deploy-only server also doesn't do JMX requests or management requests to see if the module was properly published. The intention of the deploy-only server is simply to create the war, in either exploded or zipped format, in a given folder, for users to potentially copy/paste, scp, rsync, or do whatever else. The deploy-only server also has support for zipping, which the user can configure. The only thing the deploy-only server even mentions that might make it seem jboss-specific is some text on the deployments tab, and that is only because the work to change some of the labels / options was more than I thought was reasonable at the time. Question: If the deploy-only server is expected to place a .dodeploy marker, is it also expected to read the resultant markers for a .deployed? How would this function when used against a tomcat server? Or a glassfish server? Or a fuse server? Clearly placing a .dodeploy marker is not reasonable in 90% of the different possibilities for the deploy-only server is likely to be used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)