Expose import projects command #746
Conversation
snjeza
changed the title
snjeza
changed the title
|
Just an idea come up in my mind: how about prompt users to import if we detect the workspace contains valid project? Take an example of the C# extension, when user opens a C# project folder, it will pop up a dialog to ask user if he want's to add required assets for build/debug: We can do the same thing, the Java Language Server can run in syntax mode by default, if it detects there is any build configuration files, then asks user to import it as a Java project. We can benefit from this experience by:
|
|
|
It doesn't work: If I have a multimodule Maven project, add a new module under the parent project, import doesn't find anything |
|
The succession of merge commits is just a huge mess. |
Signed-off-by: Sheng Chen <sheche@microsoft.com>
|
@fbricon The commits are rebased, could you please try again? I tried both multi-module Maven/Gradle, both can detect new sub-module and generate |
|
@fbricon If still not working, is it possible to share the project to let me diagnostic? |
|
I opened an empty folder, then in vscode's terminal, I did
|
package.json
Outdated
| @@ -553,6 +553,11 @@ | |||
| "title": "Update project configuration", | |||
| "category": "Java" | |||
| }, | |||
| { | |||
| "command": "java.project.import", | |||
| "title": "Import Java projects in workspacce", | |||
Signed-off-by: Sheng Chen <sheche@microsoft.com>
|
So this time, when calling the command, the extension activated, importing the project as part of the server startup, but ended up failing: |
|
I keep calling the import new project command, now the server is started, but still see the "No delegateCommandHandler for java.project.import" error |
|
Sorry, looks like a PEBCAK. I didn't rebuild the proper server branch |
fbricon
changed the title
See eclipse-jdtls/eclipse.jdt.ls#144
Requires eclipse-jdtls/eclipse.jdt.ls#901
Signed-off-by: Snjezana Peco snjezana.peco@redhat.com