redhat-developer / redhat-developer/vscode-java
Removing the JRE System Library from Classpath
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
I'm unable to find a way to remove the JRE System Library from the project classpath.
Eclipse has generally had the ability to remove the System Library from classpath.
Environment
- Operating System: Windows 11 Beta (had issues on 10 as well)
- JDK version: 8 and 11 - both unable to remove
- Visual Studio Code version: 1.59.1
- Java extension version: v0.81.0
Steps To Reproduce
- Open a project, and attempt to remove the JRE System Library.
- This is not possible.
A "sample" project is available at https://github.com/VivoKey/vk-u2f. The error itself is on loading CTAP2.java.
Current Result
Unable to remove JRE System Library
Expected Result
To be able to remove the JRE system library
Additional Informations
The requirement to remove JRE System Library is for programming in JavaCard, which does not use the standard Java libraries but provides it's own. I've been ignoring the issue for a while but have now found an error where using an Exception class throws build errors in VS Code (the other builds work as normal, as they don't use the system library) due to the JavaCard library also providing a java.lang.Exception.
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
Reproduce the problem with the linked VivoKey/vk-u2f sample, focusing on CTAP2.java and its JavaCard library usage. Inspect how the Java project classpath is configured and run the project build to establish the current failure. Done means the JRE System Library can be removed and CTAP2.java builds without the conflicting standard Exception class.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100