Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Packages cannot be resolved

See original GitHub issue

From @sh-tech on February 15, 2019 1:59

Enviroment

macOS Mojave 10.14.3
Visual Studio Code 1.31.1
Java Test Runner 0.14.0

issue

I want to use jUnit 5 on VSCode so I use Java Test Runner. However after installation console display errors saying can not be resolved for jUnit5. How can I solve it? Please tell me solution. I have finished setting Java’s PATH.

Images

Copied from original issue: Microsoft/vscode-java-test#616

Issue Analytics

State:
Created 5 years ago
Comments:15 (1 by maintainers)

Top GitHub Comments

1reaction

yaohaizhcommented, Feb 15, 2019

From @testforstephen on February 15, 2019 2:24

@sh-tech Could you try the command below?

0reactions

An7Onecommented, Jun 8, 2020

@polyg7ot Only groovy based build.gradle files are supported. See https://github.com/redhat-developer/vscode-java/wiki/Gradle-Support#known-limitations for more on limitations of Gradle support.

Thanks. But somehow it used to work before. At that time, I did not pay much attention. What could be the reason by any chance please?

DANG! I just realize that I can switch back to Groovy based build.gradle lol.

Top Results From Across the Web

Solved: Imported Packages Cannot be resolved

Solved : Hi All, I am getting the above dependency issues in system console, but my build is successful in eclipse. I checked...

Eclipse error: "The import XXX cannot be resolved"

I solved it by removing the project (do not delete on the disk) and importing ... So right click on the project in...

Imported packages cannot be resolved #208 - GitHub

Build fails with error that imported packages cannot be resolved. Reproduce Scenario (including but not limited to).

import cannot be resolved, but package and class exists - Bugs

Bug 131760 - import cannot be resolved, but package and class exists ... classes in packages *before* com.ezrez.common (alphabetically) are OK but classes ......

"Cannot resolve symbol" in package import

It means that semantic import versioning is not followed in k8s.io/client-go dependency. You can get the same error from the terminal by ...