[FELIX-5255] Reduce number of permutations to validate if the number gets too great to be reasonable

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: resolver-1.8.0
• Component/s: Resolver
• Assignee: Unassigned
• Reporter: Tom Watson
• Created: 11/May/16 18:10
• Updated: 11/May/16 18:52

Description

As discussed on the Felix dev mailing list:

Improve the algorithm to ignore many permutations when
the sheer number of permutations gets "too high". Before moving to the
Felix resolver in Equinox we had an algorithm that detected that number of
permutations was "too high" and would start treating multiple requirements
that point to the identical list of matching capabilities as a "single"
requirement and would permute all the identical candidate lists at the same
time instead of trying each one individually. It is possible this would
remove some valid permutations, but I had never found a real world scenario
where this approach failed to find a valid solution if one existed. The
trick here is to come up with some policy that makes sense to determine the
number of permutations is getting "too high".

I think FELIX-5254 should before this is looked at.