[jbosstools-issues] [JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed
Rob Stryker (JIRA)
issues at jboss.org
Wed Oct 29 08:51:35 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015826#comment-13015826 ]
Rob Stryker commented on JBIDE-17180:
-------------------------------------
Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=449183 for a small bug relating to server editor parts and their displayed error messages
> 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.x
>
>
> 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 was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the jbosstools-issues
mailing list