In mx/projects, I had to add a dependency such that project A was dependent on project B. But B was already dependent on A, which seemed to get the mx dependency processor into a loop. Is this a bug in mx, or should I rearrange things so there is not such a loop in the dependency graph? -- Tom