]
Martin Malina closed JBIDE-16505.
---------------------------------
Verified in JBDS 8.0.0.Alpha2a B70.
Tried WildFly 8.0.0.Final, EAP 6.2.0.GA, EAP 5.2.0.GA.
Deployment marker not removed when removing exploded war from EAP6
------------------------------------------------------------------
Key: JBIDE-16505
URL:
https://issues.jboss.org/browse/JBIDE-16505
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Alpha2
Environment: JBT 4.2.0.Alpha2 B54
EAP 6.2.0
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Labels: respin-a
Fix For: 4.2.0.Alpha2
When you start EAP 6.2 and deploy an exploded war on it, it deploys fine. But when you
remove said module from the server (in server view), the dir is removed without notifying
the server first - autodeploy of exploded wars is off in EAP 6 by default. And the
.deployed file stays behind in the deployments folder.
{code}
17:22:48,563 WARN [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads -
2) JBAS015006: The deployment scanner found that the content for exploded deployment
jboss-as-kitchensink-html5-mobile.war has been deleted, but auto-deploy/undeploy for
exploded deployments is not enabled and the jboss-as-kitchensink-html5-mobile.war.deployed
marker file for this deployment has not been removed. As a result, the deployment is not
being undeployed, but resources needed by the deployment may have been deleted and
application errors may occur. Deleting the jboss-as-kitchensink-html5-mobile.war.deployed
marker file to trigger undeploy is recommended.
{code}
As a consequence, when you deploy the module again, the server console shows:
{code}
17:20:38,251 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565:
Replaced deployment "jboss-as-kitchensink-html5-mobile.war" with deployment
"jboss-as-kitchensink-html5-mobile.war"
{code}
And when you remove the module and then stop the server, the .deployed marker is still
there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: