-
Notifications
You must be signed in to change notification settings - Fork 150
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
14871 add testrunner #602
Conversation
f603894
to
a832339
Compare
@@ -0,0 +1,24 @@ | |||
apiVersion: v2 | |||
publisher: redhat | |||
name: java |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be java8
@tsmaeder Happy Path PR check [build 282] failed.Re-trigger by
Depending on failure reason, the artifacts or deployment may not be present. |
@tsmaeder Happy Path PR check [build 283] failed.Re-trigger by
Depending on failure reason, the artifacts or deployment may not be present. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
We should probably deprecate |
@tsmaeder Happy Path PR check [build 284] failed.Re-trigger by
Depending on failure reason, the artifacts or deployment may not be present. |
[ci-test-happy-path] |
Happy path tests passed. |
There was probably some glitch... I couldn't reproduce this running the tests locally and next run of the PR check succeeded. |
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. |
@tsmaeder Happy Path PR check [build 301] failed.Re-trigger by
Depending on failure reason, the artifacts or deployment may not be present. |
[ci-test] |
@tsmaeder Happy Path PR check [build 303] failed.Re-trigger by
Depending on failure reason, the artifacts or deployment may not be present. |
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 |
- 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 | ||
|
There was a problem hiding this comment.
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.
@tsmaeder Happy Path PR check [build 310] failed.Re-trigger by
Depending on failure reason, the artifacts or deployment may not be present. |
[ci-test-happy-path] |
@tsmaeder Happy Path PR check [build 311] failed.Re-trigger by
Depending on failure reason, the artifacts or deployment may not be present. |
[ci-test-happy-path] |
@tsmaeder Happy Path PR check [build 312] failed.Re-trigger by
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>
594ec63
to
c856d3a
Compare
I've rebased this PR |
@tsmaeder Happy Path PR check [build 332] failed.Re-trigger by
Depending on failure reason, the artifacts or deployment may not be present. |
Superseded by #619 |
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