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

Resolver 1.9.0 #736

Closed
wants to merge 1 commit into from
Closed

Resolver 1.9.0 #736

wants to merge 1 commit into from

Conversation

cstamas
Copy link
Member

@cstamas cstamas commented Nov 21, 2022

Resolver 1.9.0 has a breaking change MRESOLVER-284 that was later undone (in 1.9.1+). Hence, the
CLI changes are needd ONLY for 1.9.0 and shall be
removed on upgrade to later version.

Still, the patch is incomplete, as it merely sets
mvnd specific defaults, but does not allow
mvnd users to override locking (to HZ/redisson
for example).

Resolver 1.9.0 has a breaking change MRESOLVER-284
that was later undone (in 1.9.1+). Hence, the
CLI changes are needd ONLY for 1.9.0 and shall be
removed on upgrade to later version.

Still, the patch is incomplete, as it merely sets
mvnd specific defaults, but does not allow
mvnd users to override locking (to HZ/redisson
for example).
@cstamas cstamas self-assigned this Nov 21, 2022
@cstamas
Copy link
Member Author

cstamas commented Nov 21, 2022

Hm, this patch was originally made against mvnd 0.9.0 and it worked well. On master it seems both resolver get into dist (so both, resolver 1.8.2 and 1.9.0) and it causes havoc.

@gnodet
Copy link
Contributor

gnodet commented Nov 23, 2022

Superseded by #742

@gnodet gnodet closed this Nov 23, 2022
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