[
https://issues.jboss.org/browse/JBIDE-18912?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-18912:
-------------------------------------
To be clear, the issue here is that the error message does not inform the user to also
check "add missing deployment scanners". So this basically requires an
additional check and an updated error message.
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)