[jbosstools-issues] [JBoss JIRA] (JBIDE-21637) Deploy-only does not create .dodeploy marker

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-21637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158336#comment-13158336 ] 

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. 

> Deploy-only does not create .dodeploy marker
> --------------------------------------------
>
>                 Key: JBIDE-21637
>                 URL: https://issues.jboss.org/browse/JBIDE-21637
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.3.1.Beta2
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>
> When you create a deploy-only server adapter, point it to a deployment dir of a running WildFly server and then deploy a project (exploded war, which is the default), the server will say:
> {code}
> 14:17:45,258 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0004: Found jboss-kitchensink.war in deployment directory. To trigger deployment create a file called jboss-kitchensink.war.dodeploy
> {code}
> I'm not exactly sure if the deploy-only server adapter should do this or not - how can it know if you want it or not. But Max says it should work and is a bug if it doesn't.
> One workaround is to use zipped deployment in the server adapter settings. Another would be to change your server not to require the marker and deploy everything immediately. But it would be best if this just worked without any intervention.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)