Dubious package detection for empty standalone files

[pluckhuang]

Issue Type: Bug

a.java empty file in package A, i write "package A", then notice me "The declared package "A" does not match the expected package ""Java(536871240)", however, i move this a.java to B directory, then move back to A directory, this notice disappear! why is it..

VS Code version: Code 1.30.0 (c6e592b, 2018-12-11T22:22:15.793Z)
OS version: Darwin x64 18.2.0

[yaohaizh]

@hjb912 What the type of your project? Could you provide a gif for reproducing this issue.
Thanks.

[danjmillier]

I'm also getting this same error myself:

[fbricon]

@danjmillier can you reload vscode?

[danjmillier]

@fbricon I've tried reloading and even restarting my laptop, still no dice. Oddly enough, if I make a "main2" folder and change "package main" to "package main2" it works and I'm not sure why..

[fbricon]

So this is caused by jdt.ls's invisible project mechanism, that initializes it's source directory as "_/whatever/package", because the opened Java file was empty, so the initial package could not be inferred.

[the1derer]

I am also facing the same issue.

[yaohaizh]

@testforstephen Could you help investigate this issue?

[testforstephen]

When the language server is activated by an empty standalone java file, a new idea is trying to search a non empty java file from the same directory. If found, use the non empty java file to resolve package name, otherwise, take the workspaceRoot as source root and then the relative path to workspaceRoot should be the package name.

@fbricon any thoughts?

[fbricon]

yeah you can try that