[jbosstools-issues] [JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed
[
https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-17180:
-------------------------------------
Experiencing following stacktrace:
{code}
!STACK 0
java.lang.NullPointerException
at
org.jboss.ide.eclipse.as.ui.editor.internal.JBossDeploymentOptionsComposite$RadioClickedCommand.execute(JBossDeploymentOptionsComposite.java:581)
at
org.eclipse.wst.server.ui.internal.command.ServerCommand.execute(ServerCommand.java:39)
at
org.eclipse.wst.server.ui.internal.editor.GlobalCommandManager.executeCommand(GlobalCommandManager.java:345)
at
org.eclipse.wst.server.ui.internal.editor.ServerResourceCommandManager.execute(ServerResourceCommandManager.java:54)
at org.jboss.ide.eclipse.as.ui.editor.DeploymentPage.execute(DeploymentPage.java:117)
at
org.jboss.ide.eclipse.as.ui.editor.internal.JBossDeploymentOptionsComposite.radioSelected(JBossDeploymentOptionsComposite.java:486)
at
org.jboss.ide.eclipse.as.ui.editor.internal.JBossDeploymentOptionsComposite$2.widgetSelected(JBossDeploymentOptionsComposite.java:288)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
{code}
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)