You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a package Foo is opened that has dependencies that themselves depend on Foo then things go awry: the principal package is not being taken into account when the build tree is compiled, leading to a wrong result.
Since this is a pretty rare scenario it did not come to light until recently. CodeCoverage is an example: for development it depends on Tester2 which in turn depends on CodeCoverage.
The text was updated successfully, but these errors were encountered:
When a package
Foo
is opened that has dependencies that themselves depend onFoo
then things go awry: the principal package is not being taken into account when the build tree is compiled, leading to a wrong result.Since this is a pretty rare scenario it did not come to light until recently.
CodeCoverage
is an example: for development it depends onTester2
which in turn depends onCodeCoverage
.The text was updated successfully, but these errors were encountered: