We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
As I was having some problems with the extension, I created a blank dev container (java, bullseye-21), and clones the sample projects of junit5: (got directed there from https://code.visualstudio.com/docs/java/java-testing > https://github.com/junit-team/junit5-samples)
In the testing tab, no tests are being found. And no green arrows appear next to the tests:
Building it using mvn (not mvnw as it complains about "cannot read distributionUrl property in ./.mvn/wrapper/maven-wrapper.properties") works fine:
All the while no tests are being found, and the extension is searching for tests for over an hour already (see first and second image).
The text was updated successfully, but these errors were encountered:
Reverting to version 1.41 of the Language Support for Java(TM) by Red Hat extension will work. If you use this.
Sorry, something went wrong.
It works - thank you for the quick help.
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
As I was having some problems with the extension, I created a blank dev container (java, bullseye-21), and clones the sample projects of junit5: (got directed there from https://code.visualstudio.com/docs/java/java-testing > https://github.com/junit-team/junit5-samples)
In the testing tab, no tests are being found. And no green arrows appear next to the tests:
Building it using mvn (not mvnw as it complains about "cannot read distributionUrl property in ./.mvn/wrapper/maven-wrapper.properties") works fine:
All the while no tests are being found, and the extension is searching for tests for over an hour already (see first and second image).
The text was updated successfully, but these errors were encountered: