Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-26331

Server adapter: switching maven profile (which determines the war name) won't undeploy the old war nor deploy the new one

XMLWordPrintable

      steps:

      1. EXEC: create the "hello" application in OpenShift as outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello.adoc#option-2-deploy-project-via-oc-cli
      2. EXEC: import the "hello" maven project into your Eclipse
      3. EXEC: create a server adapter and start it
      4. ASSERT: server adapter for project "hello" is [Started, Synchronized]
      5. ASSERT: "openshift" maven profile is activated for the "hello" project, console output for oc rsync shows that a war called "ROOT.war" was deployed.
      6. EXEC: in the Project Explorer: pick Maven > Select Maven Profiles... and uncheck the "openshift" maven profile
      7. ASSERT: Console output for oc rsync shows that a war "hello.war" was published

      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 that confirms this:

      [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
      
      �[0m�[0m13:06:03,938 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war")
      

              Unassigned Unassigned
              adietish@redhat.com André Dietisheim
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: