Open kharybdys opened 3 years ago
First analysis suggests because the dependency logic only remembers the attributes of the current dependency and does not recurse or inherit the tenant specifity of its own include.
Note that more tests in the same class fail for this reason. They have this issue number next to them as a marker to turn them back on once fixed
See the junit tests in BundleManipulationTest, test testBundleCreationWithDoubleLayerInclude. The final assertion should work but it currently fails.
It is verified that the current navajo system also exhibits the same, wrong, behaviour.