]
Andre Dietisheim updated JBIDE-26331:
-------------------------------------
Summary: Server adapter: switching maven profile (which determines the war name)
won't undeploy the old war nor deploy the new one (was: Server adapter: switching
maven profile (which determines the war name) won't undeploy the old war)
Server adapter: switching maven profile (which determines the war
name) won't undeploy the old war nor deploy the new one
-------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-26331
URL:
https://issues.jboss.org/browse/JBIDE-26331
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.9.0.AM2
Reporter: Andre Dietisheim
steps:
# EXEC: create the "hello" application in OpenShift as outlined in
https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...
# EXEC: import the "hello" maven project into your Eclipse
# EXEC: create a server adapter and start it
# ASSERT: server adapter for project "hello" is *[Started, Synchronized]*
# ASSERT: *"openshift"* maven profile is activated for the "hello"
project, console output for oc rsync shows that a war called "ROOT.war" was
deployed.
# EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... and uncheck the
"openshift" maven profile
# ASSERT: Console output for oc rsync shows that a war "hello.war" was
deployed
Result:
A new war "hello.war" was published but not deployed - no .dodeploy marker was
created - , the old war "ROOT.war" was *NOT* removed and is still deployed.
In the Pod log you see the following output for wildfly/eap
{code}
[0m[0m13:05:47,443 INFO [org.jboss.as.server.deployment.scanner]
(DeploymentScanner-threads - 1) WFLYDS0004: Found hello.war in deployment directory. To
trigger deployment create a file called hello.war.dodeploy
{code}
{code}
[0m[0m13:06:03,938 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39)
WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war")
{code}