Projects which have linked resources is not supported well.

[fbricon]

I'm currently trying to integrate https://github.com/jbangdev/jbang-eclipse with jdt.ls, which kinda worsS, but I noticed the Java Projects view doesn't show the JBang classpath container defined in https://github.com/jbangdev/jbang-eclipse/blob/main/dev.jbang.eclipse.core/plugin.xml#L38. In Eclipse it looks like:

The label is defined in https://github.com/jbangdev/jbang-eclipse/blob/main/dev.jbang.eclipse.core/src/main/java/dev/jbang/eclipse/core/internal/classpath/JBangClasspathContainer.java#L26, but I don't know if there's an easy way to get to that, using JDT's API.

In any case, not showing the dependencies at all is very annoying.

[jdneo]

Is there any steps to play with it?

Looks like related with https://github.com/microsoft/vscode-java-dependency/blob/main/jdtls.ext/com.microsoft.jdtls.ext.core/src/com/microsoft/jdtls/ext/core/PackageCommand.java#L258. Need a sample to debug.

[fbricon]

See attached extension and demo file: jbang-demo.zip

• unzip and install vsix
• open jbangscript folder
• open hello.java

You should see a JBang Discovery build step in the Java status
This is still highly experimental, there are some issues with the JBang builder so you might see some compilation errors. Try deleting / re-adding the //DEPS com.github.lalyos:jfiglet:0.0.9 line (or change version to 0.0.8 or lower)

There might be some conflicts between the Java version configured for the invisible project, vs the java version configured by the //JAVA comment, but that's another issue.

[fbricon]

You should be able to get the proper label of any classpath container from

IClasspathContainer container = JavaCore.getClasspathContainer(classpathEntry.getPath(), javaProject);
return container.getDescription()

[jdneo]

Still investigating the issue. Some findings:

After import the sample project, there are two projects imported:

• hello.java - The JBang project
• jbangscript_xxxxx - The invisible project

When passing the proejct folder jbangscript's uri to the code here

vscode-java-dependency/jdtls.ext/com.microsoft.jdtls.ext.core/src/com/microsoft/jdtls/ext/core/PackageCommand.java

Line 615 in 6d48fad

IContainer[] containers = root.findContainersForLocationURI(JDTUtils.toURI(projectUri));

returns the invisible project, which does not contain the JBang classpath entry.

[fbricon]

Updated extension, only the JBang project is created. It's now even worse, the project doesn't show up in the manager
jbang-demo.zip

[jdneo]

Still see multiple projects imported in the workspace storage. I installed the vsix in the latest zip file and cleaned the workspace cache.

Anyway, since the uri passed to the Java code is the folder opened in VS Code, and that's a linked folder of the invisible project, so the current implementation is not aware of the imported JBang project in the workspace cache. Looks like we need to introduce some new strategies to handle this kind of (not only for JBang) situation.

---

Update:

It's because the two vsix files have different publisher id, after uninstall all the jbang extensions and install the latest one, now I can only see the JBang projects imported.

[fbricon]

No it shouldn't generate the invisible project. Make sure you delete ~/Library/Application Support/Code/CachedExtensionVSIXs before installing the vsix

[jdneo]

Root cause found:

It's here

vscode-java-dependency/jdtls.ext/com.microsoft.jdtls.ext.core/src/com/microsoft/jdtls/ext/core/ProjectCommand.java

Lines 110 to 111 in 6d48fad

	if ((!ResourceUtils.isContainedIn(project.getLocation(), paths)
	&& !Objects.equals(project.getName(), invisibleProjectName))) {

We limit to only support invisible project when the project uri is out of the workspace.

[fbricon]

I've published the code to my extension to https://github.com/fbricon/vscode-jbang. Updated vsix can be found in https://github.com/fbricon/vscode-jbang/releases/tag/latest

EDIT: code has now moved to https://github.com/jbangdev/jbang-vscode

[jdneo]

Thanks for the update @fbricon. Will take a look when I have time :)

[fbricon]

And pre-releases are now available on https://marketplace.visualstudio.com/items?itemName=jbangdev.jbang-vscode