On 14-10-10 12:33, Patricia Shanahan wrote:
Do any of your unit tests test the Jini implementation, independent of
the rest of your own code? If so, please consider contributing them, so
that they can be run as part of the build tests. The more unit tests,
from the more different sources, the better.
One way of minimizing pain during a package reorganization would be to
go through a step of having both old and new versions of the classes,
with the old versions unmodified except for being deprecated. Code using
the classes could be modified gradually to remove references to
deprecated classes.
Some remarks:
* a.Thing.class != b.Thing.class
* discipline to maintain svn revision history
* extend and deprecate? final classes?
I prefer big bang conversion.
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
