[jbosstools-issues] [JBoss JIRA] (JBIDE-18912) Custom deploy dir with remote server using filesystem operations does not work

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-18912:
---------------------------------------

This is the log from server start:
{code}
09:39:08,685 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 2621ms - Started 151 of 189 services (56 services are lazy, passive or on-demand)
09:39:08,796 INFO  [org.jboss.as.protocol] (Remoting "marvin:MANAGEMENT" read-1) JBAS012119:  cancelled task by interrupting thread Thread[management-handler-thread - 1,5,management-handler-thread]
09:39:08,858 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/rasp/tmp/deploy
09:39:23,875 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
09:39:35,044 INFO  [org.jboss.as.protocol] (Remoting "marvin:MANAGEMENT" read-1) JBAS012119:  cancelled task by interrupting thread Thread[management-handler-thread - 1,5,management-handler-thread]
{code}
As you can see sometimes this "cancelled task" thing happens, but I'm not sure if it's relevant here and why it happens. But the main thing is that in this instance no .dodeploy was created.

> Custom deploy dir with remote server using filesystem operations does not work
> ------------------------------------------------------------------------------
>
>                 Key: JBIDE-18912
>                 URL: https://issues.jboss.org/browse/JBIDE-18912
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.1.CR1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>
> This is a follow up of JBIDE-17180 and JBIDE-13445 which added the option to add a custom deployment directory if your remote server is using filesystem operations (for management api it's not relevant since the deployment happens directly, no directory is used).
> Unfortunately it does not work. It seems I haven't really tried it when reviewing those other JIRAs because there were other obstacles.
> I tried this several times and still could not get it to work.
> Perhaps it might be worth to try and get this in the final 4.2.1.Final build?



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)