| Eclipse Che Documentation

Adding plug-ins

Che 7 plug-ins replace Che 6 installers. The following table lists the Che 7 plug-ins that have replaced Che 6 installers.

Table 1. Che 7 plug-ins that have replaced Che 6 installers
Che 6 installer	Che 7 plug-in
org.eclipse.che.ws-agent	Deprecated and not necessary
org.eclipse.che.terminal	Deprecated and not necessary anymore-
org.eclipse.che.exec	Che machine-exec Service
org.eclipse.che.ls.java	Language Support for Java

Prerequisites

A running instance of Eclipse Che. To install an instance of Eclipse Che, see Che 'quick-starts'.
An existing workspace defined on this instance of Eclipse Che Creating a workspace from user dashboard.

Procedure

To add plug-ins to your workspace:

Click the Plugins tab.
Enable the plug-in that you want to add and click the Save button.

Defining the workspace editor

Prerequisites

A running instance of Eclipse Che. To install an instance of Eclipse Che, see Che 'quick-starts'.
An existing workspace defined on this instance of Eclipse Che Creating a workspace from user dashboard.

Procedure

To define the editor to use with the workspace:

Click the Editors tab.

The recommended editor for Che 7 is Che-Theia.
Enable the editor to add and click the Save button.
Click the Devfile tab to view the changes.

Defining specific container images

Procedure

To add a new container image:

Copy the following section from the devfile into components:

- mountSources: true
   command:
     - sleep
   args:
     - infinity
   memoryLimit: 1Gi
   alias: maven3-jdk11
   type: dockerimage
   endpoints:
     - name: 8080/tcp
       port: 8080
   volumes:
     - name: projects
       containerPath: /projects
   image: 'maven:3.6.0-jdk-11'

When using type: kubernetes or type: openshift, you must:

Use seperate recipe files.

To use separate recipe files, the paths can be relative or absolute. For example:

...
    type: kubernetes
    reference: deploy_k8s.yaml
...

...
    type: openshift
    reference: deploy_openshift.yaml
...

Alternatively, add the content as referenceContent (the referenceContent field replaces the Che 6 recipe content).

Add a Che 6 recipe content to the Che 7 devfile as referenceContent:
1. Click the Containers tab (Workspace → Details → Containers).
2. Copy the Che 6 recipe, and paste it into the separate Che 7 component as a referenceContent.
3. Set the type from the original Che 6 configuration. The following is an example of the resulting file:
  type: kubernetes referenceContent: | apiVersion: v1 kind: Pod metadata: name: ws spec: containers: - image: 'rhche/centos_jdk8:latest' name: dev resources: limits: memory: 512Mi

Copy the required fields from the old workspace (image, volumes, endpoints). For example:

Table 2. Сhe 6 and Сhe 7 equivalence table
Che 6 workspace configuration	Che 7 workspace devfile
`environments['defaultEnv'].machines['target'].servers`	`components[n].endpoints`
`environments['defaultEnv'].machines['machineName'].volumes`	`components[n].volumes`
`environments['defaultEnv'].recipe.type`	`components[n].type`
`environments['defaultEnv'].recipe.content`	`components[n].image`

Change the memoryLimit and alias variables, if needed. Here, the field alias is used to set a name for the component. It is generated automatically from the image field, if not set.
```
  image: 'maven:3.6.0-jdk-11'
  alias: maven3-jdk11
```
Change the memoryLimit field to specify the RAM required for the component.
```
  alias: maven3-jdk11
  memoryLimit: 256M
```
Open the Devfile tab to see the changes.
Repeat the steps to add additional container images.

Adding commands to your workspace

The following is a comparison between workspace configuration commands in Che 6 (Figure 1) and Che 7 (Figure 2):

Figure 1. An example of the Workspace configuration commands in Che 6

Figure 2. An example of the Workspace configuration commands in Che 7

Table 3. Сhe 6 and Сhe 7 equivalence table
Che 6 workspace configuration	Che 7 workspace devfile
`environments['defaultEnv'].commands[n].name`	`commands[n].name`
`environments['defaultEnv'].commands[n].actions.command`	`components[n].commandLine`

Procedure

To define commands to your workspace, edit the workspace devfile:

Add (or replace) the commands section with the first command. Change the name and the command fields from the original workspace configuration (see the preceding equivalence table).
```
commands:
  - name: build
    actions:
      - type: exec
        command: mvn clean install
```
Copy the following YAML code into the commands section to add a new command. Change the name and the command fields from the original workspace configuration (see the preceding equivalence table).
```
  - name: build and run
    actions:
      - type: exec
        command: mvn clean install && java -jar
```
Optionally, add the component field into actions. This indicates the component alias where the command will be performed.
Repeat step 2 to add more commands to the devfile.
Click the Devfile tab to view the changes.
Save changes and start the new Che 7 workspace.