]
Michelle Murray updated JBIDE-14001:
------------------------------------
Release Notes Docs Status: Documented as Resolved Issue
Release Notes Text: On the first IDE and server restart or the first workspace
and server restart after marking a new file as deployable, the file was no longer
deployed. At the session restart, there was no check to ensure the deployed file IDs
matched those in the previous session. This issue has been resolved by ensuring that the
file is properly found during the next session and now marking a new file as deployable
persists from one session to the next.
First restart of JBDS/App Server results in deployed archive being
deleted from deploy directory.
-------------------------------------------------------------------------------------------------
Key: JBIDE-14001
URL:
https://issues.jboss.org/browse/JBIDE-14001
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.0.1.Final
Environment: Windows 7
Reporter: David Stephan
Assignee: Rob Stryker
Fix For: 4.2.0.CR2
After Marking a jar as deployable and deploying to EAP server, the jar is deployed
correctly.
Then, after restarting JBDS, then restarting the app server from within JBDS, the
deployed jar is deleted.
After restarting the server again, the jar is deployed, and subsequent restarts don't
remove the jar.
Possibly related, when you first mark the jar as deployable and deploy to a server, the
context menu item changes to "Unmark as Deployable." After a restart of JBDS,
this context menu item is back to "Mark as Deployable".