[KARAF-4701] forcing deterministic heuristic of capbillities comparison for Subsystem Resolver #291
Conversation
This file contains 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
…on for Subsystem Resolver
|
R: @jbonofre |
JiriOndrusek
pushed a commit
to JiriOndrusek/karaf-1
that referenced
this pull request
Apr 17, 2019
[ENTESB-9567] Use jline 3.6.2.redhat-2
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.
When some bundle exactly duplicated in two or more installing features Felix Resolver may randomly chose one that not already installed.
Karaf already use some hack for deterministic resolution in CandidateComparator. But as now it can't produce stable result for absolutly identical bundles.
This patch expand deterministic resolution hack to use Requirement identity in comparison, ie compare from witch feature/subsystem/region bundle is coming.
Steps to reproduce described in bug report. All version from 4.0.6 up to current master is affected. But with Felix Resolver 1.12.0 it is harder to reproduce.