Disabling maven importer prevents project from being imported at all. about eclipse.jdt.ls HOT 5 CLOSED

The lightweight mode ("java.server.launchMode": "LightWeight") can satisfy your need. It can provide reference navigation between your own source code, but it doesn't cover the dependencies.

from eclipse.jdt.ls.

@ethan-vanderheijden Could you attach a project example?

from eclipse.jdt.ls.

my_project
│   pom.xml
│   
└───src
    └───main
        └───java
            └───my_package
                    Foo.java

Foo.java and pom.xml can both be empty. Disable "java.import.maven.enabled" and run "Java: Clean Java Language Server Workspace". Then, open up Foo.java and you should see the yellow squiggle saying this is a non-project file.

You can force the project to be imported as a standard project in two ways:

• rename "pom.xml" to anything else
• create a java file at the project root

If it is supposed to fall back on the standard importer when the maven/gradle importer is disabled, I think the fix is as simple as checking if maven/gradle is disabled here:

from eclipse.jdt.ls.

I don't think this is a typical scenario. The question is why you want to use InvisibleProjectImporter to import your project instead of Maven importer?

from eclipse.jdt.ls.

We don't support Maven projects in our environment, and I was caught a little off guard when disabling Maven turned everything into non-project files. At first, I thought that falling back to the invisible project importer would allow some language features (e.g. resolving references between files) to start working again, but in retrospect, this doesn't make much sense. After all, if I turn off Maven projects, I should expect that they aren't supported.

from eclipse.jdt.ls.