spring-projects / spring-projects/spring-boot
Create a StandardJarScanner that can handle nested URLs directly
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
Currently StandardJarScanner.process calls org.apache.tomcat.util.scan.JarFactory to create a org.apache.tomcat.Jar instance. Our new nested jar code will result in org.apache.tomcat.util.scan.JarFileUrlJar which is not very performant. We might be able to create our own Jar implementation and a StandardJarScanner subclass to use it.
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 reading StandardJarScanner.process and how it uses org.apache.tomcat.util.scan.JarFactory to create org.apache.tomcat.Jar instances. Investigate the nested-jar path involving JarFileUrlJar, then determine the design for a Jar implementation and StandardJarScanner subclass that handle nested URLs directly. Done means the scanner avoids the less-performant JarFileUrlJar path for nested jars.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100