You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
Hi @GC-3 - it seems like your $CLASSPATH variable isn't set correctly since javac can't resolve the symbols. The .classpath-file is generated by the Eclipse IDE and can contain references to additional classes.
It depends on your development setup if you have a .classpathfile or not. But you'll need at least a correct $CLASSPATH variable (see this help for further information) set up to hint javac where to search for your additional classes.
Hello,
I was able to fix this by setting the working directory of javac to the project root dir instead of the path of the source file to be linted. I'd really appreciate a review of my PR, because if my proposed fix works on other systems too, it would improve the user experience of this package immensely, as then you wouldn't need to manually configure classpaths anymore.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When linting a class, it shows an error when importing custom classes:
Is this caused by an incorrect .classpath file? If so, how does one create a .classpath file properly? I have found little information on its subject.
The text was updated successfully, but these errors were encountered: