[jira] [Updated] (FELIX-5255) Reduce number of purmutations to validate if the number gets to great too be reasonable

["Thomas Watson (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FELIX-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Watson updated FELIX-5255:
---------------------------------
    Summary: Reduce number of purmutations to validate if the number gets to great too be reasonable  (was: Reduce number of purmutations to validate if the number gets to great to be reasonable)

> Reduce number of purmutations to validate if the number gets to great too be reasonable
> ---------------------------------------------------------------------------------------
>
>                 Key: FELIX-5255
>                 URL: https://issues.apache.org/jira/browse/FELIX-5255
>             Project: Felix
>          Issue Type: Bug
>          Components: Resolver
>    Affects Versions: resolver-1.8.0
>            Reporter: Thomas Watson
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)