spring-projects / spring-projects/spring-tools
implement prototype for using new javac-based JDT parser
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 983
- Forks
- 240
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 7
Description
The majority of the information around the incubated version of JDT that allows you to switch between javac and ejc-based parsing of Java source code can be found here: https://github.com/redhat-developer/vscode-java/releases/tag/v1.36.0
The idea here is to build a prototype of the spring boot language server that uses this incubating version of JDT with javac-based parsing enabled. Questions would be:
- what do we need to change in order to adopt this?
- parsing source code (bulk)
- parsing source code (single file)
- caching the environment (to speed-up lookup when re-parsing a file)
- what are the performance implications of this? (running sample projects of up to 60k source files)
- what are the memory implications of this? (running sample projects of up to 60k source files)
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
Read the incubated JDT details in the linked vscode-java v1.36.0 release first, then inspect how the Spring Boot language server currently parses Java source and caches its environment. Prototype javac-based parsing for bulk and single-file cases, and compare performance and memory on sample projects of up to 60k source files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- compilers, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100