Resource folders shown empty in JARs in Java Project View

[jfrantzius]

Hi,
with "Language Support for Java" v. 1.50.0, the Java Projects View shows empty folders within all JARs in my Maven Dependencies, although they do contain files.
In contrast, in Eclipse in the "Package Explorer View", the same folders in those JARs properly show their contained folders and files.

Please see screenshots, please note that the "dam-app-jcr" folder in VS Code is in expanded state, but shows nothing.

VS Code:

Eclipse:

[apupier]

The little arrow close to the dam-app-jcr is on the right in VS Code, which suggest that it is is collapsed. Bt you mention that i tis is "expanded state", so do you mean that when trying to expand it, it stays with collapsed state?

[jfrantzius]

Hi :)
Sorry I had uploaded the VS Code screenshot with the ">" arrow in the wrong state, it was in non-expanded state. Going to correct it in the description...

[fbricon]

I could reproduce with

<dependency>
  <groupId>info.magnolia.dam</groupId>
  <artifactId>magnolia-dam-jcr</artifactId>
  <version>4.0.9</version>
  <exclusions>
      <exclusion>
          <groupId>*</groupId>
          <artifactId>*</artifactId>
      </exclusion>
  </exclusions>
</dependency>
...

  <repositories>
    <repository>
      <id>magnolia</id>
      <url>https://nexus.magnolia-cms.com/content/repositories/magnolia.public.releases/</url>
      <releases>
        <enabled>true</enabled>
      </releases>
    </repository>
  </repositories>

There's an error in the logs:

!ENTRY org.eclipse.jdt.ls.core 4 0 2025-12-01 12:32:01.533
!MESSAGE Error in calling delegate command handler
!STACK 0
java.lang.NullPointerException
	at java.base/java.util.Objects.requireNonNull(Objects.java:220)
	at java.base/java.util.Arrays$ArrayList.<init>(Arrays.java:4197)
	at java.base/java.util.Arrays.asList(Arrays.java:4181)
	at com.microsoft.jdtls.ext.core.PackageCommand.getFolderChildren(PackageCommand.java:462)
	at com.microsoft.jdtls.ext.core.PackageCommand.getChildren(PackageCommand.java:110)
	at com.microsoft.jdtls.ext.core.CommandHandler.executeCommand(CommandHandler.java:31)
	at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler$1.run(WorkspaceExecuteCommandHandler.java:230)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
	at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler.executeCommand(WorkspaceExecuteCommandHandler.java:220)
	at org.eclipse.jdt.ls.core.internal.handlers.JDTLanguageServer.lambda$4(JDTLanguageServer.java:620)
	at org.eclipse.jdt.ls.core.internal.BaseJDTLanguageServer.lambda$0(BaseJDTLanguageServer.java:87)
	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:667)
	at java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:504)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:511)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1450)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:2019)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:187)

The error is caused by the Project Manager for Java extension, please open a ticket in https://github.com/microsoft/vscode-java-dependency/issues.
cc @testforstephen @wenytang-ms @chagong

[jfrantzius]

Alright, thank you very much for looking into this!