redhat-developer / redhat-developer/vscode-java
java build shows missing com/sun/java/tools/17.0.7/tools-17.0.7.jar in my maven path
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Type: Bug
My java settings
"java.jdt.ls.java.home": "/Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home",
"java.configuration.runtimes": [
{
"name": "JavaSE-1.8",
"path": "/Library/Java/JavaVirtualMachines/jdk1.8.0_251.jdk/Contents/Home",
"default": true
},
{
"name": "JavaSE-11",
"path": "/Library/Java/JavaVirtualMachines/jdk-11.0.16.1.jdk/Contents/Home"
},
{
"name": "JavaSE-17",
"path": "/Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home"
}
],
The error shows below.
[Error - 11:17:08 AM] May 30, 2023, 11:17:08 AM Error occured while building workspace. Details:
message: The container 'Maven Dependencies' references non existing library '/Users/zhangyongfeng/.m2/repository/com/sun/java/tools/17.0.7/tools-17.0.7.jar';
I cannot find any tools.jar under java 17.0.7, so this should be a bug.
And it is strange that only one of my java project is impacted, and others not.
Extension version: 1.19.2023052604
VS Code version: Code - Insiders 1.79.0-insider (Universal) (667d4629dee90744edd5054f13bc2452c8c14490, 2023-05-29T05:24:34.999Z)
OS version: Darwin x64 22.3.0
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | 2, 3, 3 |
| Memory (System) | 16.00GB (0.20GB free) |
| Process Argv | --crash-reporter-id e54c087f-256d-45e7-820b-0b56af32ddb5 |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
vscod805cf:30301675
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30404738
cppdebug:30492333
vscaac:30438845
vsclangdf:30492506
c4g48928:30535728
dsvsc012:30540252
pynewext54:30618038
pylantcb52:30590116
pyind779:30611226
pythonsymbol12:30651887
2i9eh265:30646982
showlangstatbar:30737417
pythonms35:30671666
03d35959:30680466
57b77579:30687741
pythonfmttext:30716741
pythoncmvfstr:30726892
fixhidewlkth:30724384
showsbindicator:30724477
pythongtdpath:30726887
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Maven Dependencies error with the reported Java 8, 11, and 17 runtime configuration and compare the affected project with the projects that work. Trace why the workspace references com/sun/java/tools/17.0.7/tools-17.0.7.jar; done means the affected workspace builds without referencing a missing Java 17 library.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, vscode
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100