Various issues with stacks on OSIO

[ibuziuk]

there are currently 7 osio specific che recipes and quite a few would be added during the codenvy.io -> che.openshift.io transition - https://github.com/redhat-developer/che-dockerfiles/tree/master/recipes
All the stacks should work with the default recommended projects OOTB:

• centos-nodejs
• centos_dotnet20
• centos_jdk8
• spring-boot
• ubuntu_jdk8
• vertx
• wildfly-swarm

Related bugs:

• Invalid "Preview:" URL in Spring and Nodejs stacks with respective samples Invalid "Preview:" URL in Spring and Nodejs stacks with respective samples #820
• .NET workspace - quickstart has lot of error markers .NET workspace - quickstart has lot of error markers #805

Problems description:

1. centos-nodejs / image registry.devshift.net/che/centos-nodejs
workspace starts correctly so image seems to be fine. When imported with nodejs-hello-world and executing nodejs-hello-world:run / run commands preview url is parsed correctly but not accessible since preview url points to ${server.8080/tcp}

with web-nodejs-simple project:

build command works fine.

web-nodejs-simple:run: (preview url is not parsed correctly)

run (funny thing that app.js is not even located in the app folder but rather in the scripts )

2. separate issue for centos_dotnet20 stack / registry.devshift.net/che/centos_dotnet20 - #505

3. centos_jdk8 / registry.devshift.net/che/centos_jdk8
workspace strartup works fine and all commands for console-java-simple project. However, for web-java-spring preview url ${server.tomcat8} is not parsed correctly:

[amisevsk]

The wildfly-swarm stack has an issue due to the booster artifact being renamed: #764

[amisevsk]

Old issue pertaining to dotnet image: #505

Need to install lang server for dotnet to work.

[amisevsk]

Some preview urls are broken in default build/run commands. E.g. for web-java-spring sample project, I see preview URL as ${server.tomcat8}, so something is going wrong.

[rhopp]

.NET image: Workspace startup is successful with redhat-developer/che-dockerfiles#37, but there are lot of error markers in sourcecode:

Building and running works fine, with one minor drawback - The preview link is not resolved correctly:

One has to go to servers and take the preview URL from there.

[ibuziuk]

Closing in favour of #1434