the nightly build is compiled and used for testers. so that might limit some testers.
========================= BJ Freeman http://bjfreeman.elance.com Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93> Specialtymarket.com <http://www.specialtymarket.com/> Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Linkedin <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> Adrian Crum sent the following on 4/17/2010 9:07 AM: > 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 > > > > >
