uninstall -f -all does not seem to do it in an intelligent order
when performing
uninstall -f -all
We have module A which is our bootstrap that all ofther modules depend on. If we uninstall module H it will uninstall module A before doing B,C,D etc.
Some of our classes in B thru H implement ClassProjections and as part of deleting the classes in module B thru H it calls %RemoveProject but %RemoveProject was part of module A.
I have also experienced this issue multiple times. Likely a bug in the way in which all dependency graphs are merged together or processing of it to determine the correct order in which to uninstall
Discussed with @SCanzano today - this fits with the other uninstall fixes in v0.10.3
@SCanzano do you have details on the topology or other factors that cause this? I've tried creating a series of test modules that rely in a single module A but uninstall -f -all is able to correctly determine the ordering.
uninstall -all has changed its internal workings as of 0.10.4 so this should hopefully be fixed.