Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Upgrade VS Code Metals, the Scala language client, to version 1.9.5 #668

Closed

Conversation

sideeffffect
Copy link
Contributor

Signed-off-by: sideeffffect [email protected]

@che-bot
Copy link
Contributor

che-bot commented Nov 5, 2020

Can one of the admins verify this patch?

1 similar comment
@che-bot
Copy link
Contributor

che-bot commented Nov 5, 2020

Can one of the admins verify this patch?

@sideeffffect sideeffffect changed the title Upgrade VS Code Metals, the Scala language client, to version 1.9.5 [WIP] Upgrade VS Code Metals, the Scala language client, to version 1.9.5 Nov 5, 2020
firstPublicationDate: "2020-11-02"
spec:
containers:
- image: "quay.io/gattytto/scala090:0.9.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's different about this image? It's probably best to update the side in che-sidecar-scala, no?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've created a ticket to fix the image che-dockerfiles/che-sidecar-scala#10

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

when this one is merged you may use the new sidecar ID for quay.io/eclipse/che-sidecar-scala:0.9.0-xyz here @sideeffffect

@@ -344,7 +344,7 @@
},
{
"repository": "https://github.com/scalameta/metals-vscode",
"revision": "v1.9.4",
"revision": "v1.9.5",
"sidecar": {
"image": "quay.io/eclipse/che-sidecar-scala:0.9.0-b92a5f9",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here you will need to use the new ID after https://github.com/eclipse/che-plugin-registry/pull/682/files is merged @sideeffffect

ericwill and others added 8 commits November 10, 2020 22:44
* FUSETOOLS2-805 - update didact version to 0.1.18

Signed-off-by: [email protected] <[email protected]>

* update vscode-extensions.json

Signed-off-by: [email protected] <[email protected]>
* hlasm-language-support 0.11.1

New version of plugin hlasm-language-support 0.11.1

Signed-off-by: Filip Kroupa <[email protected]>

* Remove hlasm-language-support 0.11.0

Remove older plugin version, as only one should be in the registry. See eclipse-che/che#18183

Signed-off-by: Filip Kroupa <[email protected]>
* Plugin registry housekeeping

* Remove old didact extension
* Delete redhat/php plugin as we have the latest one under the publisher name
* Move redhat/php-debug to the proper publisher/plugin-name folder

Signed-off-by: Eric Williams <[email protected]>

* Fix vscode-php-debug publisher name and name in meta.yaml

Signed-off-by: Eric Williams <[email protected]>

* Re-introduce php-debugger, deprecate and set correct plugin as migrateTo

Signed-off-by: Eric Williams <[email protected]>

* Fixup description and remove extra line

Signed-off-by: Eric Williams <[email protected]>
…he#676)

* Move sidecar definitions into the plugin registry

Part 1 of the migration. I am doing it in parts because doing it all at once
will likely cause a build timeout upon pushing.

Part of eclipse-che/che#18217

Signed-off-by: Eric Williams <[email protected]>

* Handle java and java8 separately

Signed-off-by: Eric Williams <[email protected]>
Includes fixes to the before-start.sh script to prevent shellcheck failures.

Signed-off-by: Eric Williams <[email protected]>
@sideeffffect
Copy link
Contributor Author

deprecated by #685

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants