Skip to content

Bug: Settings interpolation and strict parsing - #11776

Merged
cstamas merged 1 commit into
apache:maven-3.10.xfrom
cstamas:maven-3.9.x-settings
Apr 8, 2026
Merged

Bug: Settings interpolation and strict parsing#11776
cstamas merged 1 commit into
apache:maven-3.10.xfrom
cstamas:maven-3.9.x-settings

Conversation

@cstamas

@cstamas cstamas commented Mar 10, 2026

Copy link
Copy Markdown
Member

Problem: today in none of Maven 3 is possible to use placeholders and apply interpolation to non-String fields (ie proxy.active or proxy.port). Moreover, given Maven is "forgiving" in settings parsing, and only WARNs, it is very easy for user to miss information.

This PR:

  • fixes interpolation for whole settings
  • allows users to apply "strict" settings parsing that makes Maven FAIL if settings was not properly parsed or interpolated by setting -Dmaven.settings.strictParsing in user or system properties.

Fixes #11011

Problem: today in none of Maven 3 is possible to use placeholders
and apply interpolation to non-String fields (ie proxy.active
or proxy.port). Moreover, given Maven is "forigiving" in settings
parsing, and only WARNs, it is very easy for user to miss information.

This PR:
* fixes interpolation for whole settings
* allows users to apply "strict" settings parsing that makes Maven
  FAIL if settings was not properly parsed or interpolated
@cstamas cstamas self-assigned this Mar 10, 2026
@cstamas cstamas added this to the 3.10.0 milestone Mar 10, 2026
@cstamas cstamas added the bug Something isn't working label Mar 10, 2026
@cstamas cstamas changed the title Bug: Settings interpolation and strict Bug: Settings interpolation and strict parsing Mar 10, 2026
@cstamas
cstamas marked this pull request as ready for review March 10, 2026 12:51
@cstamas

This comment was marked as outdated.

@michael-o

Copy link
Copy Markdown
Member

There should be some old PR and issue for that. Did you take a look? AFAIR it was done by either @hboutemy or @rfscholte .

@cstamas
cstamas changed the base branch from maven-3.9.x to maven-3.10.x March 25, 2026 15:49
@cstamas

cstamas commented Mar 25, 2026

Copy link
Copy Markdown
Member Author

Why would I look for old issue that was done?

@michael-o

Copy link
Copy Markdown
Member

Why would I look for old issue that was done?

For reference

@cstamas

cstamas commented Apr 8, 2026

Copy link
Copy Markdown
Member Author

For reference

I cannot find any related PR.

@cstamas
cstamas merged commit 24deab9 into apache:maven-3.10.x Apr 8, 2026
18 checks passed
@cstamas
cstamas deleted the maven-3.9.x-settings branch April 8, 2026 15:00
@slawekjaranowski

Copy link
Copy Markdown
Member

@cstamas

cstamas commented Apr 14, 2026

Copy link
Copy Markdown
Member Author

Yes, once the 'sprint' for 3.10.x is done, we will need forward porting stuff. Same for version filters, it is much improved compared to 4 (inclusion added, h/l is G:A addressable, etc).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support JVM-Config and environment variables for proxy configuration

3 participants