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

Errors reported for java files belonging to a non default project, but not on its classpath #456

Closed
fbricon opened this issue Nov 21, 2017 · 0 comments
Assignees
Labels

Comments

@fbricon
Copy link
Contributor

fbricon commented Nov 21, 2017

Following up on #453, when a java file belongs to a project, but is not in an actual source folder, compilation errors should be ignored.
Because it already belongs to a project, it's probably not a good idea to link it to the default project either. Which means that file should not receive any java support whatsoever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants