Separating out the test from the code is a recognized well established pattern for java development. I like it.
----- "Adrian Crum" <[email protected]> wrote: > Right now the test classes are included in each component's jar file. > It seems to me it might save on memory or the target server's disk > space if the test classes were left out of the component's final jar > file. > > Maybe have a folder structure something like: > > component > src > main > org > ofbiz > etc... > test > org > ofbiz > etc... > > The main branch is for the deployment jar and the test branch is only > for test classes. The end result would be you could have a separate > build for the test classes that wouldn't put them in the final jar. > Another advantage is the test classes can be in the same package as > the classes they test. (The current setup is a pain in that respect.) > > What do you think? > > -Adrian
