feature: Add "path" to webapp generator

[rhuss]

and also fix the assembly to include the proper artefact, regardless
of the 'final' name.

Fixes #1276.

[rhuss]

Added a new feature 'path' which use the root context path as default ("/"). This is also a perfect fit to the generate route on OpenShift (which otherwise wouldn't find the service because it does not know about the context path).

Currently, it doesn't work with the Tomcat base image because of permission problems when overwriting the ROOT dir. This will be fixed asap with fabric8io-images/tomcat#2

[rohanKanojia]

Thanks a lot, I tested it and now I don't see error even when finalName is not set

[rohanKanojia]

@rhuss : Did you tested it on Openshift/Kubernetes? Actually, I was testing it on Openshift(in -Dfabric8.mode=kubernetes) but application pod goes in ImagePullBackOff state(Might be some problem with my Openshift)

[rhuss]

I tested it with minishift and it worked as expected.

[rhuss]

btw, ne Tomcat images has been fixed, released and f-m-p uses them. These images fixes the problem with root context.

I'm going probably to update Jetty and Wildfly Images soon, too, to use the latest upstream servers.

[rhuss]

@rohanKanojia if you use openshift, please be sure that the user part of your image is the same as the projectname in OpenShift.

That's what I did in samples/webapp

mvn package fabric8:build fabric8:resource fabric8:apply -Dfabric8.generator.webapp.server=jetty -Dfabric8.generator.name="myproject/%a:%l"

assuming that I'm connected to a project "myproject". Also note, that %l as there are still problems with the default %t which should have been changed already as it really gives you all sort of problems. See #1093 and and #1270

[rohanKanojia]

@rhuss : Works, Thanks.