Re: [che-dev] New model for Che 7 plugin meta.yaml - incompatible change

[Sun Tan <sutan@xxxxxxxxxx>]

the answer is:
1. find the path of your plugin from https://github.com/eclipse/che-plugin-registry/tree/master/v2/plugins

2. replace id with it
so the previous example would look like this

```

  - 

    type: chePlugin

    id: eclipse/che-machine-exec-plugin/0.0.1

  - 

    type: chePlugin

    id: redhat/vscode-yaml/0.4.0

  - 

    type: chePlugin

    id: che-incubator/typescript/1.30.2

```

Sun TAN
Senior Java Software Engineer
Eclipse Che - Openshift.io @ Red Hat
Paris JUG team member

Mobile : +33 6 21 02 41 73
Email : sutan@xxxxxxxxxx 
Email Paris JUG : sunix@xxxxxxxxxxxx
Blog: http://blog.sunix.org
twitter: @sunsengdavidtan 

----------------------------

On Fri, May 3, 2019 at 4:54 PM Sun Tan <sutan@xxxxxxxxxx> wrote:

Hello,
Could you sumarize what need to be changed ? 
For instance if I am using a devfile with 

```

 - 

    type: chePlugin

    id: che-machine-exec-plugin:0.0.1

  - 

    type: chePlugin

    id: redhat.vscode-yaml:0.3.0

  - 

    type: chePlugin

    id: ms-vscode.typescript:1.30.2

```

How should it be now ?

Thanks

Sun TAN
Senior Java Software Engineer
Eclipse Che - Openshift.io @ Red Hat
Paris JUG team member

Mobile : +33 6 21 02 41 73
Email : sutan@xxxxxxxxxx 
Email Paris JUG : sunix@xxxxxxxxxxxx
Blog: http://blog.sunix.org
twitter: @sunsengdavidtan 

----------------------------

On Fri, May 3, 2019 at 12:58 PM Oleksandr Garagatyi <ogaragat@xxxxxxxxxx> wrote:

Hello, all.

As part of the merging meta.yaml and che-plugin.yaml  (issue https://github.com/eclipse/che/issues/12908) we are about to do some changes in Che that are not backward compatible.

Even though it is backward incompatible change for plugins it WON'T break existing workspaces if they are not using Che 7 plugins hosted in custom registries. If you didn't put custom plugin registry reference in your workspace config manually you are fine and change should not affect you.

It will affect custom registries though. To see how to migrate custom registries see https://github.com/eclipse/che-plugin-registry/pull/135 and https://github.com/eclipse/che/issues/12908#issuecomment-474312103.

We have already merged changes in Che plugin registry https://github.com/eclipse/che-plugin-registry/pull/135 but they are not enabled in Che yet. After PR https://github.com/eclipse/che-plugin-broker/pull/55 is merged we will update Che to use this new model for meta.yaml.

You can follow its status in PR https://github.com/eclipse/che/pull/13276 that brings it to Che.

We are very sorry for the inconvenience it can bring.

If you have any questions or want more information, do not hesitate to ping us in che-dev mailing list or file a Github issue https://github.com/eclipse/che/issues.

--

OLEKSANDR GARAGATYI

SENIOR SOFTWARE ENGINEER

Red Hat 

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev