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

14871 add testrunner #602

Closed
wants to merge 4 commits into from

Conversation

tsmaeder
Copy link
Contributor

@tsmaeder tsmaeder commented Sep 1, 2020

What does this PR do?

Adds the Java testrunner extension to all Java-related plugins. The version is 0.24.0, since 0.24.1 requires Java 11 to run.

This issue fixes Installing Java Test Runner Support for Java eclipse-che/che#14871

@@ -0,0 +1,24 @@
apiVersion: v2
publisher: redhat
name: java
Copy link
Contributor

Choose a reason for hiding this comment

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

Should be java8

@che-bot
Copy link
Contributor

che-bot commented Sep 1, 2020

@tsmaeder Happy Path PR check [build 282] 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/282/console
artifacts http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/282/

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

@che-bot
Copy link
Contributor

che-bot commented Sep 1, 2020

@tsmaeder Happy Path PR check [build 283] 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/283/console
artifacts http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/283/

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

Copy link
Contributor

@svor svor left a comment

Choose a reason for hiding this comment

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

LGTM

@ericwill
Copy link
Contributor

ericwill commented Sep 1, 2020

We should probably deprecate 0.63.0 and set it to migrate to 0.63.0a

@che-bot
Copy link
Contributor

che-bot commented Sep 1, 2020

@tsmaeder Happy Path PR check [build 284] 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/284/console
artifacts http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/284/

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

@rhopp
Copy link
Contributor

rhopp commented Sep 4, 2020

[ci-test-happy-path]

@che-bot
Copy link
Contributor

che-bot commented Sep 4, 2020

Happy path tests passed.

@rhopp
Copy link
Contributor

rhopp commented Sep 4, 2020

There was probably some glitch... I couldn't reproduce this running the tests locally and next run of the PR check succeeded.

@tsmaeder
Copy link
Contributor Author

tsmaeder commented Sep 7, 2020

We should probably deprecate 0.63.0 and set it to migrate to 0.63.0a

Hhmh...why? If anything, shouldn't we deprecate 0.57? 0.63 works just fine, and if the user wants the new features, he can update by hand. There is nothing special about 0.63a except that the version of vscode-java did not change.

@che-bot
Copy link
Contributor

che-bot commented Sep 8, 2020

@tsmaeder Happy Path PR check [build 301] 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/301/console
artifacts http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/301/

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

@tsmaeder
Copy link
Contributor Author

tsmaeder commented Sep 8, 2020

[ci-test]

@che-bot
Copy link
Contributor

che-bot commented Sep 8, 2020

@tsmaeder Happy Path PR check [build 303] 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/303/console
artifacts http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/303/

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

@ericwill
Copy link
Contributor

ericwill commented Sep 8, 2020

We should probably deprecate 0.63.0 and set it to migrate to 0.63.0a

Hhmh...why? If anything, shouldn't we deprecate 0.57? 0.63 works just fine, and if the user wants the new features, he can update by hand. There is nothing special about 0.63a except that the version of vscode-java did not change.

I suppose it could be optional, but it would be nice to have all users be able to take advantage of the new test runner support out of the box, and it's not immediately obvious that such new features are available just by visual inspection. Since there is no vscode-java version change from 0.63.0 to 0.63.0a it's a harmless migration.

- https://download.jboss.org/jbosstools/vscode/3rdparty/vscode-java-debug/vscode-java-debug-0.26.0.vsix
- https://download.jboss.org/jbosstools/static/jdt.ls/stable/java-0.63.0-2222.vsix
- https://open-vsx.org/api/vscjava/vscode-java-test/0.24.0/file/vscjava.vscode-java-test-0.24.0.vsix

Copy link
Contributor

Choose a reason for hiding this comment

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

Extra newlines/missing newling at EOF? Looks like something weird happened here.

@che-bot
Copy link
Contributor

che-bot commented Sep 9, 2020

@tsmaeder Happy Path PR check [build 310] 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/310/console
artifacts http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/310/

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

@tsmaeder
Copy link
Contributor Author

tsmaeder commented Sep 9, 2020

[ci-test-happy-path]

@che-bot
Copy link
Contributor

che-bot commented Sep 9, 2020

@tsmaeder Happy Path PR check [build 311] 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/311/console
artifacts http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/311/

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

@tsmaeder
Copy link
Contributor Author

tsmaeder commented Sep 9, 2020

[ci-test-happy-path]

@che-bot
Copy link
Contributor

che-bot commented Sep 9, 2020

@tsmaeder Happy Path PR check [build 312] 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/312/console
artifacts http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/312/

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

Signed-off-by: Thomas Mäder <tmader@redhat.com>
Signed-off-by: Thomas Mäder <tmader@redhat.com>
Signed-off-by: Thomas Mäder <tmader@redhat.com>
Signed-off-by: Thomas Mäder <tmader@redhat.com>
@benoitf
Copy link
Contributor

benoitf commented Sep 11, 2020

I've rebased this PR

@che-bot
Copy link
Contributor

che-bot commented Sep 11, 2020

@tsmaeder Happy Path PR check [build 332] 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/332/console
artifacts http://artifacts.ci.centos.org/devtools/che/che-plugin-registry-prcheck/332/

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

@ericwill
Copy link
Contributor

Superseded by #619

@ericwill ericwill closed this Sep 11, 2020
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