[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=13323736#comment-13323736 ] 

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

[~rob.stryker], my steps clearly included checking "Expose management port":
{quote}
2. Open server editor and check "Expose management port", check "Add scanners" and "Remove scanners", make sure the password is OK
{quote}

Also, when I tried this now, at first I had my admin password incorrect which resulted in an error in the Error log view.
But once I fixed that, I followed the steps again and I can still reproduce the issue:
First attempt to deploy into custom directory works, the project is found and deployed.
Second attempt fails, the project is found, but not deployed:
{code}
14:50:16,568 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /home/rasp/jbossqa/runtimes/jboss-eap-6.4.0/customdir
14:50:41,596 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
{code}

To repeat, these are my steps to reproduce:
1. Create a remote server (remote, fs operations, no runtime) - eap 6.3
2. Open server editor and check "Expose management port", check "Add scanners" and "Remove scanners", make sure the password is OK
3. Go to Deployment tab in the editor, set up a custom dir on the remote host for deployment, save the editor
4. Create a simple dynamic web project
5. Start the server, in the server log you will see that the custom deployment scanner was added
6. Deploy your project (right-click server -> Add/Remove modules)
7. Check the server console - the project was deployed
8. Undeploy the project
9. Stop the server
10. Repeat 5. and 6., this time it will copy the project, but not create the .dodeploy marker, so the project will not deploy.
11. If you remove the project and deploy again now, it will work. But if you go all over again (i.e. new server start) it will not work

> 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
>              Labels: help_wanted
>             Fix For: 4.4.2.Final
>
>
> 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
(v7.2.3#72005)