How should multiple (related) projects be arranged (structured) and configured so that they can share code, have a related package structure and enable proper unittesting, and ensuring no namespace collisions

[alisonken1]

It can be fun when talking several subjects in the same post <g>.

In this case, it was just a matter of thinking about what the main
question was about unit testing code that also required other
production packages, but with the caveats that he didn't want to
duplicate packages just to test code or hack around during testing,
then have to change the test code when it was time to add to production
code (which may introduce more errors that the testing would not find).

CVS just found it's way from one of the suggestions as a side note in
reply to a minor point about how to keep track of test code without
messing with/duplicating production code.