microsoft / microsoft/vscode-java-dependency
Need absolute path for third librairies
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- TypeScript
- Estrellas
- 199
- Forks
- 105
- Merge medio
- 1 d 22 h
- PR fusionados (30 d)
- 27
Descripción
I can't add manually my jar to my project in any way.
First, I made a lib folder and add on the configuration file :
{
"java.compile.nullAnalysis.mode": "disabled",
"java.project.referencedLibraries": [
"lib/**/*.jar"
]
}
Didn't works, the jar is not referenced.
I tried to add it with the project setting pane, get an error :
!ENTRY org.eclipse.jdt.ls.core 4 2 2026-02-12 07:53:10.315
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jdt.ls.core".
!STACK 0
org.eclipse.jdt.internal.core.ClasspathEntry$AssertionFailedException: Path for IClasspathEntry must be absolute: lib/HyUI-0.8.4-all.jar
at org.eclipse.jdt.core.JavaCore.newLibraryEntry(JavaCore.java:5430)
at org.eclipse.jdt.ls.core.internal.commands.ProjectCommand.convertClasspathEntry(ProjectCommand.java:351)
at org.eclipse.jdt.ls.core.internal.commands.ProjectCommand.updateClasspaths(ProjectCommand.java:244)
at org.eclipse.jdt.ls.core.internal.JDTDelegateCommandHandler.executeCommand(JDTDelegateCommandHandler.java:104)
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:618)
at org.eclipse.jdt.ls.core.internal.BaseJDTLanguageServer.lambda$0(BaseJDTLanguageServer.java:87)
at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(Unknown Source)
at java.base/java.util.concurrent.CompletableFuture$Completion.exec(Unknown Source)
at java.base/java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source)
at java.base/java.util.concurrent.ForkJoinPool.scan(Unknown Source)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(Unknown Source)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source)
!ENTRY org.eclipse.jdt.ls.core 4 0 2026-02-12 07:53:10.317
!MESSAGE Error in calling delegate command handler
!STACK 0
org.eclipse.jdt.internal.core.ClasspathEntry$AssertionFailedException: Path for IClasspathEntry must be absolute: lib/HyUI-0.8.4-all.jar
at org.eclipse.jdt.core.JavaCore.newLibraryEntry(JavaCore.java:5430)
at org.eclipse.jdt.ls.core.internal.commands.ProjectCommand.convertClasspathEntry(ProjectCommand.java:351)
at org.eclipse.jdt.ls.core.internal.commands.ProjectCommand.updateClasspaths(ProjectCommand.java:244)
at org.eclipse.jdt.ls.core.internal.JDTDelegateCommandHandler.executeCommand(JDTDelegateCommandHandler.java:104)
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:618)
at org.eclipse.jdt.ls.core.internal.BaseJDTLanguageServer.lambda$0(BaseJDTLanguageServer.java:87)
at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(Unknown Source)
at java.base/java.util.concurrent.CompletableFuture$Completion.exec(Unknown Source)
at java.base/java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source)
at java.base/java.util.concurrent.ForkJoinPool.scan(Unknown Source)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(Unknown Source)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source)
The only solution/workaround I found, it's to put the jar outside of my project and use the project setting pane.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Reproduce el fallo con una entrada lib/**/*.jar local al proyecto en java.project.referencedLibraries y, después, sigue la conversión de ruta indicada en ProjectCommand.java en la línea 351. Confirma cómo el panel de configuración del proyecto proporciona el classpath e identifica el límite donde se rechaza la ruta relativa. Se considera terminado cuando un jar dentro del proyecto se acepta y se referencia sin la excepción de ruta absoluta.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java, typescript, vscode
- Área
- developer-experience, tooling
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 48/100