[
https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-17180:
---------------------------------------------
Not if the server is configured to pick up deployments from this location.
I don't think we should disable the option but warn for sure.
We could disable the checkbox or warn when it fails concerning adding/removing scanners.
Disable custom deployment settings for remote servers without
management port exposed
-------------------------------------------------------------------------------------
Key: JBIDE-17180
URL:
https://issues.jboss.org/browse/JBIDE-17180
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.2.0.Beta1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.2.0.Beta2
JBIDE-13445 added the possibility to use custom deploy dir on remote server.
{quote}
Remember: If a remote server is not running with its management ports exposed, do not
attempt to add the scanners, as the management connections will fail.
{quote}
We should disable this option in such case, because right now it just adds confusion -
you have a server without management port exposed and not knowing about all the details
you change the deployment dir, you will end up with non-working deployment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira