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

Resolves #888: New optional parameter to SetMojo: interpolateProperties #889

Merged

Conversation

jarmoniuk
Copy link
Contributor

  • allows to disable property interpolation, so that it's possible to match against raw property values as well as replace properties with interpolated values if the value is the same as the property value

This is my take on resolving the problem which occurs when the user wants to match against a version which is the same as the interpolated property value. If this is the case, by default, the file is left unchanged, so that it continues to contain the properties.

If the new parameter is employed, it is possible to disable interpolation for such cases, but one needs to match against the raw value (e.g. use the property name, or *), and the value will be replaced.

…Properties

- allows to disable property interpolation, so that it's possible to match against raw property values as well as replace properties with interpolated values if the value is the same as the property value
@jarmoniuk
Copy link
Contributor Author

jarmoniuk commented Dec 30, 2022

@slawekjaranowski lots of new PRs, here's one more :)

jarmoniuk added a commit to jarmoniuk/versions-maven-plugin that referenced this pull request Dec 31, 2022
…nsMojo and UseNextReleasesMojo in case of no newer versions/releases
jarmoniuk added a commit to jarmoniuk/versions-maven-plugin that referenced this pull request Dec 31, 2022
…nsMojo and UseNextReleasesMojo in case of no newer versions/releases
@jarmoniuk
Copy link
Contributor Author

@slawekjaranowski why did you close this PR?

@pzygielo
Copy link
Contributor

why did you close this PR?

Commit with closing keyword was pushed to master.

@jarmoniuk
Copy link
Contributor Author

jarmoniuk commented Dec 31, 2022

Please reopen.

Wrong commit message on that other PR. :|

@jarmoniuk
Copy link
Contributor Author

The commit message was ok: there is both an issue 889 as well as a PR 889....

@pzygielo
Copy link
Contributor

there is both an issue 889 as well as a PR 889....

Is that possible?

@jarmoniuk
Copy link
Contributor Author

@pzygielo no:

PR #889

Issue #891

@jarmoniuk
Copy link
Contributor Author

So indeed wrong commit message.

@slawekjaranowski
Copy link
Member

@slawekjaranowski why did you close this PR?

Was classed because was mentioned in merged PR

closed this in edf4e2f

@jarmoniuk
Copy link
Contributor Author

Should I create a new one?

@slawekjaranowski
Copy link
Member

Reopened 😄

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

Successfully merging this pull request may close these issues.

Regression in 2.14.2: version not updated
3 participants