Skip to content

[Backport 4.0.x] [MNG-8425] Fix mvnenc init saving invalid master source configuration - #12564

Merged
gnodet merged 1 commit into
maven-4.0.xfrom
backport/12418-mvnenc-init-fix
Jul 28, 2026
Merged

[Backport 4.0.x] [MNG-8425] Fix mvnenc init saving invalid master source configuration#12564
gnodet merged 1 commit into
maven-4.0.xfrom
backport/12418-mvnenc-init-fix

Conversation

@gnodet

@gnodet gnodet commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Backport of #12418 to maven-4.0.x.

When the encryption wizard prompts for an editable value with a template like env:$MVN_PASSWORD, the user input is now auto-prefixed with the source prefix (env:, system-property:, etc.) if missing. Adds parameterized test covering 5 prefix scenarios.

Fixes MNG-8425 / #10202

When the encryption wizard prompts for an editable value with a
template like env:$MVN_PASSWORD, the user input is now auto-prefixed
with the source prefix (env:, system-property:, etc.) if missing.
Adds parameterized test covering 5 prefix scenarios.

Fixes #10202
Closes #12418
@gnodet gnodet added this to the 4.0.0-rc-6 milestone Jul 28, 2026

@gnodet gnodet left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — clean backport of #12418 (merged on master today). The fix correctly handles mvnenc init prefix prepending for template-based configuration values (e.g., env:, system-property:), and the new InitTest provides solid parameterized coverage of the prefix logic.

This review was generated by an AI agent and may contain inaccuracies. Please verify all suggestions before applying.

Claude Code on behalf of gnodet

gnodet added a commit to gnodet/maven that referenced this pull request Jul 28, 2026
@gnodet
gnodet merged commit d498fca into maven-4.0.x Jul 28, 2026
24 checks passed
@gnodet
gnodet deleted the backport/12418-mvnenc-init-fix branch July 28, 2026 09:02
@github-actions

Copy link
Copy Markdown

@gnodet Please assign appropriate label to PR according to the type of change.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants