This is a follow up on JBIDE-22128.

The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes

steps:

1. EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello.adoc (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
2. EXEC: import the app into your Eclipse workspace
3. EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
4. EXEC: create a server adapter and start it
5. ASSERT: adapter starts syncing, verify what war is used

Result:
The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"

Expected result:
If you start the server adapter the maven profile "openshift" should be activated and the war that's published should be "ROOT.war". If you stop the server adapter the "openshift" maven profile should be deactivated for the "hello" project.