* CHE#4258 org.eclipse.che.util.GwtXmlGenerator searches for all files XXX.gwt.xml in classpath and creates uber gwt.xml. Generated gwt.xml will be used by maven-gwt-plugin to compile gwt code
* Boolean server property to enable or disable auto start of a workspace when accessing to it through its url
https://issues.jboss.org/browse/CHE-116
Signed-off-by: Sun Seng David Tan <sutan@redhat.com>
* fixup! Boolean server property to enable or disable auto start of a workspace when accessing to it through its url
* Update references to hold documentation site.
Signed-off-by: Stevan Le Meur <stevan.lemeur@gmail.com>
* Update missing readme files.
Signed-off-by: Stevan Le Meur <stevan.lemeur@gmail.com>
Changelog:
Delete old xterm view.
Move requirejs from plugin Orion to the plugin RequireJs.
Create new plugin with xterm.js.
Mavenize xterm.js build, use for build gulp tasks instead of bash scripts.
Rework GWT code for integration xterm.js.
Fix css styles for integration with GWT css resources and using Eclipse CHE white and dark themes.
Rework terminal resize mechanizm.
Signed-off-by: Aleksandr Andrienko <aandrienko@codenvy.com>
Now, docker CLI is the way to start Eclipse Che so we don't need anymore "native scripts" and Vagrantfile
command to start che is : docker run eclipse/che
to use local binaries : add -v <path-to-che-cloned-directory>:/repo
Resolves#3892.
Two API methods are available:
* _POST /api/system/stop_ - stops corresponding system services, for now it's workspace service.
Basically it stops all the RUNNING workspaces snapshotting them before if configured to do so,
also it interrupts start of currently STARTING workspaces.
* _GET /api/system/state_ - returns current system state(only status for now).
By default system status is RUNNING, but after stop is called or che server is
stopped directly system status is changed like the following:
```
RUNNING -> PREPARING_TO_SHUTDOWN -> READY_TO_SHUTDOWN
```
Status changes are followed by status changed events, to recieve these
events client has to subscribe on *system:state* channel.
So client can use different ways to track system status changes.
Doesn't matter whether API method is used or che server is stopped directly,
events will be sent anyway.
Adds class so that choice between DockerConnector and OpenShiftConnector
can be made via setting a property in che.properties. The provider is
injected instead of DockerConnector, and provides the appropriate
implementation through a get() method.
Signed-off-by: Angel Misevski <amisevsk@redhat.com>
It's very hard for plugin developers to extend assembly-ide-war.
To do that they need to copy all dependencies declared assembly-ide-war
because assembly-ide-war as war dependency can be reused in dependency section of pom.
If we package it as classes it can be reused to inject transitive dependencies
* Remove native launch of che / vagrant files
CLI is used to start che.
command is : docker run eclipse/che
to use local binaries : add -v <path-to-che-cloned-directory>:/repo
Change-Id: I8649830049974043b69f6725480c1799cfe325cd
Signed-off-by: Florent BENOIT <fbenoit@codenvy.com>
Set internal machine address by CLI from CHE_IP.
Add and fix docs in che.env.
Change behavior of default machine server address evaluation
to be similar to the previous state.
Code cleanup.
Signed-off-by: Alexander Garagatyi <agaragatyi@codenvy.com>
Max Shaposhnik