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
Suppose we opened a multi-root workspace in VS Code. Then we added a new folder into the workspace, and the added folder contains an invisible project.
Because there is no trigger files information, the Invisible project importer won't work, and if we open its java source file, the Language server will open it as a default project file.
But if we correct the rootPaths field, the InvisibleProjectImporter will be triggered to import it.
The text was updated successfully, but these errors were encountered:
The
updateWorkspaceFolders
in https:/eclipse/eclipse.jdt.ls/blob/master/org.eclipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/managers/ProjectsManager.java#L160will not update the
rootPaths
inpreferenceManager
, which will cause some unexpected behavior when usingrootPaths
. for example, here:https:/eclipse/eclipse.jdt.ls/blob/master/org.eclipse.jdt.ls.core/src/org/eclipse/jdt/ls/core/internal/handlers/DocumentLifeCycleHandler.java#L309
Suppose we opened a multi-root workspace in VS Code. Then we added a new folder into the workspace, and the added folder contains an invisible project.
Because there is no trigger files information, the Invisible project importer won't work, and if we open its java source file, the Language server will open it as a default project file.
But if we correct the rootPaths field, the
InvisibleProjectImporter
will be triggered to import it.The text was updated successfully, but these errors were encountered: