Add processing for nested modules with a parent version property#4472
Merged
sambsnyd merged 2 commits intoopenrewrite:mainfrom Oct 11, 2024
Merged
Add processing for nested modules with a parent version property#4472sambsnyd merged 2 commits intoopenrewrite:mainfrom
sambsnyd merged 2 commits intoopenrewrite:mainfrom
Conversation
…the parent version is a property
Member
|
Thanks @marcel-gepardec ! |
Contributor
|
@marcel-gepardec Since this commit, I have infinite loop since in my root pom, I have a parent. |
Member
Sorry to hear @philippe-granet ; Would you want to push that up as a fix? Should be quick to approve if it comes in. |
Contributor
|
@timtebeek Here the fix: #4598 |
This was referenced Oct 24, 2024
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's changed?
Added the ability to process projects with modules in modules where the parent version is a property.
If the project's version does not match the GroupArtifactVersion GAV or cannot be resolved with getValue() because there is no property such as the version string, each parent POM should now be checked to see if the property is set.
If no parent, including the last parent, the root POM, has a property like this, then it can proceed as usual.
If the property is in the root POM and corresponds to the version of the project, this project can be returned and further processed.
What's your motivation?
@ErhardSiegl noticed an incorrect behavior regarding the usage of openrewrite in a project with modules in modules where the parent version is a property. He always got this error message:
For reference:
rewrite.yml:
test-parent root pom:
test-common pom:
test-common-shared pom: