jamesfredley opened a new pull request, #15961:
URL: https://github.com/apache/grails-core/pull/15961

   ## Description
   
   ### What was found
   
   | Problem | Impact |
   | --- | --- |
   | Cache module still uses `concurrentlinkedhashmap-lru` | Older dependency, 
less maintained |
   | Codebase 3 recommended Caffeine migration | No current PR |
   | Public cache API must stay stable | Internals can move first |
   
   ### What changed
   
   | Area | Change |
   | --- | --- |
   | Implementation | `GrailsConcurrentLinkedMapCache` internals use Caffeine |
   | Manager | Keep public manager API |
   | Dependency | Prefer Caffeine over concurrentlinkedhashmap-lru path |
   | Docs / tests | Cache config note + behavioral Spock coverage |
   
   ### Out of scope / follow-up
   
   | Topic | Status |
   | --- | --- |
   | Renaming public classes away from ConcurrentLinkedMap | Later |
   | Full Spring Cache abstraction rewrite | Not this PR |
   | Benchmark suite vs old LRU | Follow-up |
   
   ### Related MD topics
   
   | Source | Topic |
   | --- | --- |
   | Codebase 3 | Caffeine migration from concurrentlinkedhashmap-lru |
   
   ## Contributor Checklist
   
   ### Issue and Scope
   - [x] Dependency modernization starter.
   - [x] Public cache API preserved.
   - [x] Single focused migration seed.
   - [x] Targets `8.0.x`.
   
   ### Code Quality
   - [x] Tests updated.
   - [x] Focused cache tests run.
   - [x] No mass reformatting.
   - [x] AI starting point labeled.
   
   ### Licensing and Attribution
   - [x] Apache License 2.0.
   - [x] Contributor rights confirmed.
   - [x] `ai-generated-starting-point` label applied.
   
   ### Documentation
   - [x] Cache docs updated.
   - [x] Scope explained.
   
   Assisted-by: Sisyphus:xai/grok-4.5 [gpt-coding]


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to