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

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-18912:
-------------------------------------

So, I thought I could finally replicate.  Nothing was happening. The files were copied, but no deployment. 

Then I realized I didn't check the "Expose management port" in the server editor. Once I did that, everything worked fine. 

However, I do notice an area for improvement:  when the management port is not exposed, the error message is swallowed and not presented to the user. This is obviously bad, as it gives no info for the user to pass on to us. 

I'll commit a fix that adds logging of the exception, but, again, I genuinely cannot replicate ;) 

> 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.15#6346)