This strategy can be used to check if the classpath entry is in project dependencies.
It will look if one project dependency matches with given organisation and given module name. If found, it will use the revision specified in the dependency. If not found it will look if one project dependency matches with given organisation. If found it will use both module name and revision specified in the dependency