spring-projects / spring-projects/spring-security
Final field mutation reported on Java 26
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
When running on java 26 the following warning is logged
WARNING: Final field aces in class org.springframework.security.acls.domain.AclImpl has been mutated reflectively by class org.springframework.security.acls.jdbc.BasicLookupStrategy in unnamed module @1d8bd0de (file:~/.m2/repository/org/springframework/security/spring-security-acl/7.0.5/spring-security-acl-7.0.5.jar)
WARNING: Use --enable-final-field-mutation=ALL-UNNAMED to avoid a warning
WARNING: Mutating final fields will be blocked in a future release unless final field mutation is enabled
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 reproducing the warning on Java 26 and inspect AclImpl together with BasicLookupStrategy, the classes named in the message. Trace the reflective mutation of the final field and verify that the warning is no longer logged while ACL lookup behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100