Eclipse Che is a cloud IDE and a platform for creating cloud IDE extensions. Che ships with 55 extensions for Java, JavaScript, AngularJS, git, and Docker. Package your own Che extensions to create beautiful, cross-browser developer tooling.

Che contains:

• A cloud IDE
• A set of extensions for many programming languages, source code systems, builders and runners
• A kernel for loading extensions authored as plug-ins
• Developer tooling for building and and assembling plug-ins to create new IDEs
• A set of platform APIs for developer microservices (e.g., 'build project' or 'search workspace')
• A CLI for interacting with platform APIs
• An Eclipse plug-in for editing, building and running Che projects from within Eclipse

The IDE is a browser application that is generated by compiling extensions into JavaScript. Extensions can invoke server-side APIs that run within the Che kernel. The kernel is a servlet-based framework that loads and manages extensions. The kernel can be run in any servlet container with a default bundling of Tomcat.

Che can be installed on any operating system that supports Java 1.7 - desktop, server or cloud, and Maven 3.1.1 or higher. It has been tested on Ubuntu, Linux, MacOS and Windows. Java, GWT, GIN and JavaScript are the core technologies used to build Che.

Che is open sourced under the Eclipse Public License 1.0.

git clone https://github.com/codenvy/che.git

cd che
mvn clean install
./che.sh [ start | stop ]

This builds and starts the SDK, which includes an assembly of Java and a bare minimum of extensions building plug-ins (everything required to work with Java apps and Codenvy extensions).

Che will be available at localhost:8080

• che-plugins: [A set of plugins for Eclipse Che] (http://github.com/codenvy/che-plugins)
• che-core: [Core components of Eclipse Che] (http://github.com/codenvy/che-core)
• che-depmgt: [Maven Dependency Management POM for Che projects] (http://github.com/codenvy/che-depmgt)
• che-parent: [Maven parent POM for Che projects] (http://github.com/codenvy/che-parent)

• CLI: [CLI for accessing APIs] (http://github.com/codenvy/cli)
• Eclipse Plug-In: [An Eclipse plug-in for running Che projects] (http://github.com/codenvy/eclipse-plugin)

This plugin requires npm, Yeoman, Bower and Grunt to be installed.

• npm setup guide : https://github.com/npm/npm npm is bundled with nodejs which can be downloaded from: http://nodejs.org/download/

• Yeoman (and bower / Grunt dependencies can be installed with: npm install -g yo) more details on http://yeoman.io/gettingstarted.html

1. Create, build and compile a Che extension into a Java JAR file. [Tutorial is here] (http://docs.codenvy.com/che/). You can create extension JARs within Che or your favorite IDE. Build extensions in Eclipse gives you super dev mode for Eclipse, which makes incremental compilation fast.

2. Copy the extension's JAR file to /assembly-sdk/target/tomcat-ide/ext directory of Che.

3. Execute $ ./extInstall.sh script. Che will be re-compiled with your extension. This will take a few minutes.

4. Restart Che.

Contribute:: We accept pull requests, so if you feel like contributing to the project, you are definitely welcome to do so.

Report Bugs: You can report bugs, contribute, and post on the Eclipse Che forums at [https://www.eclipse.org/forums/index.php/t/787421/] (https://www.eclipse.org/forums/index.php/t/787421/).

• Che Binaries: [http://docs.codenvy.com/download] (http://docs.codenvy.com/download/)
• Che Getting Started: [http://eclipse.org/che/] (http://eclipse.org/che/)
• Che JavaDoc: [docs.codenvy.com/che/javadoc/] (http://docs.codenvy.com/che/javadoc/)
• Che Extension Tutorials: [http://docs.codenvy.com/che/creating-extensions/#creating-che-apps] (http://docs.codenvy.com/che/creating-extensions/#creating-che-apps)

• Che Mail List: che-dev@eclipse.org
• Che Forums: https://www.eclipse.org/forums/index.php/t/787421/
• Website: eclipse.org/che
• Che Project Management Page: https://projects.eclipse.org/projects/technology.che

If not already done, Prepare the broker distribution.

To run the example, simply execute the below command from this directory:

mvn verify

This example demonstrates two servers coupled as a live-backup pair for high availability (HA) using replication and a client connection failing over from live to backup when the live broker is crashed and then back to the original live when it is restarted (i.e. "failback").

For more information on ActiveMQ Artemis failover and HA, and clustering in general, please see the clustering section of the user manual.