Skip to content

Deprecate SpelParserConfiguration constructors in favor of the builder API #37190

Closed

Description

@sbrannen

Overview

Since we now (as of Spring Framework 7.0.10) have an official builder API for SpelParserConfiguration, we should officially deprecate the current sea of overloaded constructors in that class -- thereby encouraging users to benefit from the simplicity of the builder API (or the SpelParserConfiguration.withDefaults() factory method) which is less error-prone than having to migrate to the latest-and-greatest full SpelParserConfiguration constructor every time a new property is introduced in the configuration.

Related Issues

Activity

  1. added this to the 7.1.0-M2 milestone on Aug 22, 2026
  2. self-assigned this
    on Aug 22, 2026
  3. added
    in: coreIssues in core modules (aop, beans, core, context, expression)
    on Aug 22, 2026
  4. added a commit that references this issue on Aug 22, 2026
    91eb426
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

in: coreIssues in core modules (aop, beans, core, context, expression)type: enhancementA general enhancement

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions