Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MNG-7604] Removal of pom.* interpolation makes some older plugins defunct #1137

Merged

Conversation

gnodet
Copy link
Contributor

@gnodet gnodet commented Jun 1, 2023

This reverts commit b2a21f1.

JIRA issue: https://issues.apache.org/jira/browse/MNG-7604

@gnodet gnodet added this to the 4.0.0-alpha-6 milestone Jun 1, 2023
Copy link
Contributor

@mthmulders mthmulders left a comment

Choose a reason for hiding this comment

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

Thanks for creating this one. I had no idea how to solve it, but this seems like a nice approach.

This text in the PR body caught me off guard

This reverts commit b2a21f1.

If I understand correctly, this PR doesn't revert b2a21f1, but refines or enhances it by only performing the validation if it needs to.

Out of curiosity: how does Maven determine which validation level to apply?

@gnodet
Copy link
Contributor Author

gnodet commented Jun 1, 2023

Thanks for creating this one. I had no idea how to solve it, but this seems like a nice approach.

This text in the PR body caught me off guard

This reverts commit b2a21f1.

If I understand correctly, this PR doesn't revert b2a21f1, but refines or enhances it by only performing the validation if it needs to.

Right, my original idea was to do a two step thing ...

Out of curiosity: how does Maven determine which validation level to apply?

The default value is VALIDATION_LEVEL_STRICT. When reading poms which are external to the workspace, the code usually set the validation level on the ModelBuildingRequest to VALIDATION_LEVEL_MINIMAL, as done here. I don't think other values are actually used.

gnodet and others added 2 commits June 1, 2023 22:57
…ing/ModelBuildingRequest.java

Co-authored-by: Maarten Mulders <mthmulders@users.noreply.github.com>
@mthmulders
Copy link
Contributor

Out of curiosity: how does Maven determine which validation level to apply?

The default value is VALIDATION_LEVEL_STRICT. When reading poms which are external to the workspace, the code usually set the validation level on the ModelBuildingRequest to VALIDATION_LEVEL_MINIMAL, as done here. I don't think other values are actually used.

Thanks for clarifying!

Copy link
Member

@cstamas cstamas left a comment

Choose a reason for hiding this comment

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

This change affects only master (and the preceding "removal" of interpolation as well)?

@gnodet
Copy link
Contributor Author

gnodet commented Jun 5, 2023

This change affects only master (and the preceding "removal" of interpolation as well)?

3.9 is not affected afaik, https://issues.apache.org/jira/browse/MNG-7244 was only targeted at 4.x

@gnodet gnodet merged commit ea1a280 into apache:master Jun 5, 2023
@gnodet gnodet deleted the MNG-7604-support-pom-props-from-central branch June 5, 2023 08:45
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.

3 participants