-
Bug
-
Resolution: Unresolved
-
Major
-
4.9.0.AM2
steps:
- 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
- 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 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")
- relates to
-
JBIDE-22138 Server adapter: doesn't respect openshift maven profile
- Closed
-
JBIDE-26330 Server adapter: shutting down Eclipse won't reset the maven profile that the adapter activated in the project
- Open