microsoft / microsoft/vscode-java-dependency
Need absolute path for third librairies
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 199
- Forks
- 105
- Ø Merge
- 1 T. 22 Std.
- Gemergte PRs (30 T.)
- 27
Beschreibung
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.
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Reproduziere den Fehler mit einem projektlokalen lib/**/*.jar-Eintrag in java.project.referencedLibraries und verfolge dann die gemeldete Pfadkonvertierung in ProjectCommand.java bei Zeile 351. Bestätige, wie das Projekteinstellungsfenster den classpath bereitstellt, und identifiziere die Grenze, an der der relative Pfad abgewiesen wird. Erledigt ist die Aufgabe, wenn ein jar innerhalb des Projekts akzeptiert und ohne die Ausnahme für absolute Pfade referenziert wird.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- java, typescript, vscode
- Bereich
- developer-experience, tooling
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 48/100