Add protectiondomain to expressions compiler [LUCENE-6465]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Today the classloader is somewhat hidden, you don't have a way to pass this. But since we are generating classes on the fly, we should allow it to be optionally specified.
---
Migrated from [LUCENE-6465](https://issues.apache.org/jira/browse/LUCENE-6465) by Robert Muir (@rmuir)
Attachments: [LUCENE-6465.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-6465/LUCENE-6465.patch)
Contributor guide
Research direction
Start by locating the expressions compiler and examining how its classloader is currently selected when generated classes are created. Trace the existing class-generation path and the attached LUCENE-6465.patch, then verify that callers can optionally provide a ProtectionDomain and that the default behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100