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

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

I think it's not worth pushing to maintenance.
But since we already have this JIRA, let me use it for this:
There is a problem that sometimes the project doesn't get deployed - the .dodeploy marker is not created.

First the short version: After every new server start, the first time I tried to deploy a project it didn't work - no .dodeploy was created. So I tried a new workspace and it worked on first server start, but on consequent server starts the first attempt never worked.

Long version:
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
>
> 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)