You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 17, 2021. It is now read-only.
Che should have an out-of-the-box run command (it has build and test-compile by default). The run needs to be "compile vertx:run" to properly leverage the vert.x hot redeploy. I then use Terminal to curl the endpoint https://screencast.com/t/Ye7PLsZuwbZd
Ok so that is really frustrating. Che vert.x stacks has a run command.
The problem is that in osio, when a user select create workspace, java_centos stack is always used. Even if the user has selected the vert.x base quickstart. The same applies to wildfly swarm and spring boot. Che has the stacks but these are not used in osio.
To solve that I believe we have a couple of choice:
The quick workaround: when the user select create workspace he is prompted with five options (plain java, vertx, spring boot, wildfly swarm, node js)
The long term solution: we inject a chefile at the root of the github repository when the codebase is created. The chefiles has informations about the stack image and commands definition.
From @burrsutter on June 6, 2017 15:42
https://screencast.com/t/3xjfAjqZJxR
Che should have an out-of-the-box run command (it has build and test-compile by default). The run needs to be "compile vertx:run" to properly leverage the vert.x hot redeploy. I then use Terminal to curl the endpoint
https://screencast.com/t/Ye7PLsZuwbZd
Copied from original issue: openshiftio/openshift.io#199
The text was updated successfully, but these errors were encountered: