Skip to content
New issue

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

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

Already on GitHub? # to your account

Improve speed of versions:resolve-ranges in case parents contain many version properties #1122

Merged
merged 2 commits into from
Aug 27, 2024

Conversation

m-schutte-ohra-nl
Copy link
Contributor

PR for #1121

If 'includeProperties' is null, use it to restrict the properties that are considered in the resolve-ranges mojo to those from the current project. Otherwise, user will normally have included only a subset of those.
Also added an it to cover the situation in #367 as this wasn't covered yet and led me to believe at first that setting 'includeParent' to false in the VersionPropertiesMapRequest was enough.

@slawekjaranowski
Copy link
Member

@m-schutte-ohra-nl thanks for PR

What title of PR should be ... ?

Please consider that it will be used in release notes, so what we want to say for users?

@m-schutte-ohra-nl m-schutte-ohra-nl changed the title 1121 Improve speed of versions:resolve-ranges in case parents contain many version properties Aug 12, 2024
Copy link
Member

Choose a reason for hiding this comment

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

I prefer groovy than bsh ... but it is also ok

@slawekjaranowski slawekjaranowski added this to the next-release milestone Aug 27, 2024
@slawekjaranowski slawekjaranowski merged commit 9dc5e0d into mojohaus:master Aug 27, 2024
26 checks passed
@m-schutte-ohra-nl m-schutte-ohra-nl deleted the 1121 branch August 28, 2024 07:34
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

versions:resolve-ranges very slow when parents contain lots of version properties
2 participants