Quarkus 1.6.0

[vitaliy-guliy]

Signed-off-by: Vitaliy Gulyy [email protected]

What does this PR do?

• Introduces Quarkus extension 1.6.0

Devfile to test

---
apiVersion: 1.0.0
metadata:
  name: java-quarkus-1.6.0
projects:
  -
    name: java-web-spring
    source:
      type: git
      location: "https://github.com/spring-projects/spring-petclinic.git"
      commitId: 4953f87917b449a404a7f1f4e2457836b9eafbbc

components:
  -
    type: chePlugin
    reference: >-
      https://raw.githubusercontent.com/vitaliy-guliy/che-plugin-registry/quarkus-1.6.0/v3/plugins/redhat/quarkus-java11/1.6.0/meta.yaml
    preferences:
      java.project.importOnFirstTimeStartup: 'automatic'

[che-bot]

@vitaliy-guliy Happy Path PR check [build 229] failed.

Re-trigger by [ci-test] or [ci-test-happy-path].

Link	URL
console	https://ci.centos.org/job/devtools-che-plugin-registry-pr-check-happy-path/229/console
artifacts	http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/229/

Depending on failure reason, the artifacts or deployment may not be present.

[che-bot]

@vitaliy-guliy Happy Path PR check [build 231] failed.

Re-trigger by [ci-test] or [ci-test-happy-path].

Link	URL
console	https://ci.centos.org/job/devtools-che-plugin-registry-pr-check-happy-path/231/console
artifacts	http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/231/

Depending on failure reason, the artifacts or deployment may not be present.

[svor]

@ericwill should we update vscode-extensions.json by hand?

[ericwill]

@ericwill should we update vscode-extensions.json by hand?

Yes.

[ericwill]

As @svor mentioned, please also update the revision field in the vscode-extensions.json file

[ericwill]

Please use the latest che-sidecar-java:11 image listed in the vscode-extension.json file for the quarkus extension.

[benoitf]

I'm a bit worried that by bumping vscode-java, users will have a default prompt about importing their java projects

is there a way to apply the configuration from meta.yaml ? and not to patch every devfile by adding

    preferences:
      java.project.importOnFirstTimeStartup: 'automatic'

[vitaliy-guliy]

I'm a bit worried that by bumping vscode-java, users will have a default prompt about importing their java projects

is there a way to apply the configuration from meta.yaml ? and not to patch every devfile by adding

    preferences:
      java.project.importOnFirstTimeStartup: 'automatic'

I tried to do it before, but wasn't lucky.
Adding preferences from plugin is not supported and it doesn't described in the plugin spec
https://github.com/eclipse/che-plugin-registry#plugin-meta-yaml-structure

But.. we can write a plugin. Which will read all the plugin meta.yamls and add the corresponding preferences if such present.
Or just extend the functionality of workspace plugin.

[vitaliy-guliy]

@ericwill done with vscode-extensions.json and with container version

[che-bot]

@vitaliy-guliy Happy Path PR check [build 232] failed.

Re-trigger by [ci-test] or [ci-test-happy-path].

Link	URL
console	https://ci.centos.org/job/devtools-che-plugin-registry-pr-check-happy-path/232/console
artifacts	http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/232/

Depending on failure reason, the artifacts or deployment may not be present.

[vitaliy-guliy]

[ci-test]

[che-bot]

@vitaliy-guliy Happy Path PR check [build 233] failed.

Re-trigger by [ci-test] or [ci-test-happy-path].

Link	URL
console	https://ci.centos.org/job/devtools-che-plugin-registry-pr-check-happy-path/233/console
artifacts	http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/233/

Depending on failure reason, the artifacts or deployment may not be present.

[ericwill]

Do we need the latest version of vscode-java? IMO it shouldn't be newer than what we already have in Che, unless absolutely necessary.

[che-bot]

@vitaliy-guliy Happy Path PR check [build 235] failed.

Re-trigger by [ci-test] or [ci-test-happy-path].

Link	URL
console	https://ci.centos.org/job/devtools-che-plugin-registry-pr-check-happy-path/235/console
artifacts	http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/235/

Depending on failure reason, the artifacts or deployment may not be present.