[jbosstools-issues] [JBoss JIRA] (JBIDE-14001) First restart of JBDS/App Server results in deployed archive being deleted from deploy directory.
[
https://issues.jboss.org/browse/JBIDE-14001?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-14001:
-------------------------------------
This was fixed in the linked issue. Copy-paste of the resolution comment:
Problem was in the SingleDeployableFactory, which upon restart was not making sure the
module id's matched what they did in the previous session.
This is also replicatable after any workspace restart where you have marked a new file as
deployable. The first restart after marking a new file as deployable will find that module
incorrectly during the next session. All sessions after that will work appropriately.
This is all fixed now, and, marking a new file as deployable will be persisted and found
properly during the next session.
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".
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)