With the contribution of #308, we noticed a case, that the file is still scanned as part of the impact analysis phase.
Usually, the SearchPathImpactFinder will leverage the internal cache of logical files Because the file is not know in the cache, the file will be rescanned. So, It requires to register the "unscanned" LogicalFile to the cache.
With the contribution of #308, we noticed a case, that the file is still scanned as part of the impact analysis phase.
Usually, the SearchPathImpactFinder will leverage the internal cache of logical files Because the file is not know in the cache, the file will be rescanned. So, It requires to register the "unscanned" LogicalFile to the cache.
https://github.com/IBM/dbb-zappbuild/blob/5000f02e312e99a6488a2218a84d65d05bdd8180/utilities/ImpactUtilities.groovy#L219