box dependencies not picked up in other box projects

[abrooks]

In a box containing projects A and B, with project A depending on B, a change to a version of a dependency in B is not reflected in the transitive dependencies of A.

This may be a leiningen checkouts issue or may be a box issue.

[abrooks]

This is, indeed, a known behavior of leiningen checkouts.

The box model seems to make a stronger promise about using this as a development workflow which means we need to present an honest, consistent view of the dependencies or people are going to be confused and frustrated.

This would ideally be fixed in leiningen though we likely have the ability to fix in box if there's no acceptably upstreamable fix to leiningen.