]
Martin Malina closed JBIDE-17395.
---------------------------------
Works nicely. I tried a couple of combinations (management/file operations, different
servers, server stopped/running) to assure there is no regression.
Verified in JBDS 8.0.0.Beta3 B172.
Run on server does not work if server is stopped (management
operations)
------------------------------------------------------------------------
Key: JBIDE-17395
URL:
https://issues.jboss.org/browse/JBIDE-17395
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta2
Environment: JBT 4.2 master (Beta3-v20140522-2026-B498)
EAP 6.2 / WildFly 8.0/8.1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.2.0.Beta3
When you use "Run on server" on a project and the server is stopped and uses
management operations, it won't work - meaning the server will start, server view will
show the project as deployed, but it won't be actually deployed and when the browser
opens, it will 404.
I checked that this affects both EAP 6.2 and WildFly (and most probably other similar
servers, too).