[Anthill] Handling Multiple dependency group w/ common dependencies

[Thompson, Andrew M. DOC]

I have a concern about the handling of common dependencies across dependency
groups.  Initially I had expected that if ProjectA was a member of
DependencyGroup1 and DependencyGroup2 that if a change was made to ProjectA,
that change would be rebuilt and propagated into both groups.  I discovered
however that is not the case.  If DependencyGroup1 was the first one on the
queue it would see that changes had been made and the appropriate artifacts
would get built and included in the project at the top of the dependency
tree.

It seems the only was to accomplish this would be to have multiple instances
of ProjectA one for each containing dependency group.  This not only seems
horribly clunky, but we would end up with several of these sort of
superfluous/redundant Projects on our anthill home page.

Thoughts?