On Thursday, June 7, 2001, at 05:41 PM, Jon Stevens wrote:
> We can start a testing suite in there. One "trick" that people use is
> that
> they create the same package tree as in src/java, but put the files in a
> test/java directory. That way, the testing code is in a different
> directory,
> but can be combined together with package access when needed for testing
> package private code. Does that make sense?
i've pulled some stuff together along those lines (but haven't committed
it yet)
what about building this test directory?
should i add additional tasks into the build-ecs.xml or is there a
better way?
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
