-
Notifications
You must be signed in to change notification settings - Fork 61
Classpath is incomplete from 0.6.4 #37
Comments
If you click the help link in the dialog that displays it will display information about what this error means and how to resolve it - basically it needs to find the build files. You need to open the folder at the right level for it to do this. |
I read the page, but that does not help as the project has a pom.xml file in the root just as @n00dl3 commented above. Also, as mentioned, it works fine with ide-java 0.6.0. just downgrading the package with apm and restarting atom makes it work again. Anything else I can try? |
Had the same issue, is there any way to enable verbose logging? As mentioned nothing is logged to the atom console so I'm not even sure where to start troubleshooting short of cleaning & reinstalling. Same though with downgrading to v0.6.0, that seems to work. |
Same issue but downgrading to v0.6.0 give me "Uncaught Error: Header must provide a Content-Length property." |
I've been researching this one as well because I haven't gotten a single Gradle project to work. From what I'm finding, you should always get incomplete classpath for all Maven and Gradle projects. The offending commit in ide-java being the upgrade of the Eclipse JDT. Though technically, this is really an issue of mismatching LSP usage between atom-languageclient and the Eclipse JDT LS. Issue
As a result, JDT never sees the root of your project and just sets up a barebones Java project. Proposed SolutionsBoth of these changes should probably happen, but either one would fix ide-java (once ide-java upgrades to the new versions of these dependencies).
I'll open issues for both of these and hopefully one or both will be resolved. ResearchJDT LS Logfrom
Key message being no root uri was defined atom-languageclientEnabling
atom-languageclient sends this intialization message itself by default (ide-java has not overriden this) in getInitializeParams. The InitializeParams type, also part of atom-languageclient, specifies only the Eclipse JDTIn the 0.5.0 JDT currently being used, that no root uri message occurs here. Above that line you can see it checking Notably, Atom is sending Between 0.6.0 and 0.6.1 of ide-java, The JDT dependency went from an old not final 0.1.0 (from April) to 0.3.0 (and has since moved beyond that version). LSP4J
Currently LSP4J 0.3.0 is being used by JDT. InitializeParams shows both a Language Server ProtocolLSP 3.0 indicates that rootDir has been deprecated in favor of rootUri and that if both are defined, |
Thanks for researching this! I was trying to hold off LSP 3.0 support and there wasn't any indication the new language server was breaking 2.0 support. I can add support for passing both as a subset of 3.0 support for now. |
Fixed in 0.6.6! Sorry for the delay. |
With 0.6.0 I was using ide-java with no issues (other than the auto complete bug #10 and taking 4 minutes for JDT to start up) with a big maven project.
0.6.1-3 didn't work due to #30
0.6.4-5 give me the "Classpath is incomplete" dialog
I guess the change from Eclipse JDT 0.3 to 0.5 has broken something?
There are no errors in the dev console. Tried with Atom 1.21 and 1.22.
The text was updated successfully, but these errors were encountered: