microsoft / microsoft/vscode-java-dependency
Need absolute path for third librairies
Personne n'a encore pris cette issue.
- Langage dominant
- TypeScript
- Étoiles
- 199
- Forks
- 105
- Merge moyen
- 1 j 22 h
- PR mergées (30 j)
- 27
Description
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.
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Reproduisez l’échec avec une entrée lib/**/*.jar propre au projet dans java.project.referencedLibraries, puis suivez la conversion de chemin signalée dans ProjectCommand.java à la ligne 351. Confirmez comment le volet des paramètres du projet fournit le classpath et identifiez la limite à laquelle le chemin relatif est rejeté. Le travail est terminé lorsqu’un jar situé dans le projet est accepté et référencé sans l’exception de chemin absolu.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java, typescript, vscode
- Domaine
- developer-experience, tooling
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- Calme
- Clarté
- Plutôt claire
- Accessibilité débutants
- 48/100