One thing, neither Dependency Browser nor Lukas Dependency Analyzer show a package that depends on Ma special collections tester. In the graph this is shown as none arrow pointing to the node Ma special collections tester.
Is this intentional?
Yep. As the name suggests, Ma special collections tester tests the special collections employed by Magma; most notably the critical MaHashIndex.
Or should I make Magma tester depend on Ma special collections tester even though no class of this last one is used by Magma tester?
Why create an artificial dependency?
By the moment I will force the dependency of Magma tester on Ma special collections tester in order to load it when loading Magma tester. Later we can change this if neccessary.
Ah, a tool limitation, that's why.. :(
- Chris