align default labels more closely with the `oc` CLI tooling

it seems the openshift oc tool and openshift web console prefers there to be a canonical app label on all resources relating to the same project.

We’ve traditionally gone with:

• project for the artifactId
• groups for the groupId
• version for the version

To make things more openshift console & oc friendly and similar should we switch project to app?

Am not sure if app should be fully qualified with the groupID too though? Otherwise we could easily get clashes

[jstrachan]

Yeah I guess omitting the ${groupId} would be OK - then if you wanna deploy the different apps with the same ${artifactId} but different ${groupId}s you’d either:

• use different namespaces to run them
• customize the app label/artifact ID to be more specific 😉

[jstrachan]

@rhuss we can certainly make app and/or project configurable for sure.

I think I’d prefer to just switch to app by default for consistency and avoid 2 labels as the default. There’s very little code that really depends on which one of these 2 are used really; its more just metadata thats viewed on consoles and CLIs.

So long as we’ve a simple flag folks can use to preserve project if they wish I think we’ll be good