[
https://issues.jboss.org/browse/JBIDE-11776?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-11776.
---------------------------------
Deploy only server now errors out, if the publish doesn't work. So I'm closing
this issue. But it would be nice if we could inform users that the remote host is
unavailable rather than wait what breaks which in this case is deleting of the deployment
from the server before trying to copy it there. I created a feature request here:
JBIDE-12046
Verified in jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
No errors for remote deploy only server
---------------------------------------
Key: JBIDE-11776
URL:
https://issues.jboss.org/browse/JBIDE-11776
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Reporter: Rob Stryker
Assignee: Martin Malina
Fix For: 3.3.0.CR1
If what I'm seeing is different from the original scenario, let me know and I can
create another JIRA.
My steps:
1. Create a Deploy only server pointing to a remote host.
2. Quit Eclipse
3. Make sure the remote host is not reachable
4. Start Eclipse
5. Drag a simple Dynamic Web Project on the Deploy only server in the Server View
6. ASSERT some sort of error (e.g. Cannot publish to server, server not found...)
FAIL - no error, everything seems to be ok
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira