[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22138 at 6/22/18 1:03 PM: ------------------------------------------------------------------- [~fbricon], [~rawb] to me this smells like a bug: As soon as I set the maven profile to "openshift" in the project properties (hello project), I see WebProjectConfiguratorDelegate#configureDeployedName (which is inherited from AbstractProjectConfiguratorDelegate) being invoked with the correct deployedFileName "ROOT". See https://github.com/eclipse/m2e.wtp/blob/master/org.eclipse.m2e.wtp/src/or... When I then get to the OpenShift server adapter (or any other server adapter) and pick "Add and Remove...", where I see all available modules listed in "Available", the hello project is still listed as "hello" (where it should be "hello (ROOT)"). To fix this I have to go into the properties for project "hello", look at ex. "Web Content Settings" and hit "Apply and Close". Once I did that I now see the correct module name "hello (ROOT)" in "Add and Remove...". !image-2018-06-22-19-02-57-247.png! (or https://youtu.be/A-N3D_VYqfk) Any idea what's the issue here? was (Author: adietish): [~fbricon], [~rawb] to me this smells like a bug: As soon as I set the maven profile to "openshift" in the project properties (hello project), I see WebProjectConfiguratorDelegate#configureDeployedName (which is inherited from AbstractProjectConfiguratorDelegate) being invoked with the correct deployedFileName "ROOT". See https://github.com/eclipse/m2e.wtp/blob/master/org.eclipse.m2e.wtp/src/or... When I then get to the OpenShift server adapter (or any other server adapter) and pick "Add and Remove...", where I see all available modules listed in "Available", the hello project is still listed as "hello" (where it should be "hello (ROOT)"). To fix this I have to go into the project properties for project hello and hit "Apply and Close". Once I did that and get back to "Add and Remove..." (server adapter) I now see "hello (ROOT)". Any idea what's the issue here? -- This message was sent by Atlassian JIRA (v7.5.0#75005)