However, there are three strategies here, and someone might have an opinion.
1) Split math into three pieces: base, most, tests. The last two depend on the first. 2) Split math into two pieces: math, and math-tests. All the unit tests end up in math-tests. 3) Just move the three common test support classes into src/main/java. 1) is an intractable mess. 2) works, but it's irritating to have all the unit tests in a separate project. 3) seems best to me, because there are only about 3 classes involved if the names are not misleading me here. It seems sort of nutty to either test-jar heck or a whole other project just to chase 5 or less test-support classes out of src/main/java. I'll do the same analysis for 'core' after math is set. I think this deserves consideration. It's only about two On Thu, Apr 7, 2011 at 4:00 PM, Ted Dunning <[email protected]> wrote: > I don't think we need review on this. Solving this is a very good thing. > > On Thu, Apr 7, 2011 at 8:27 AM, Benson Margulies <[email protected]> > wrote: >> >> The use of test-jar leads to problems, notably that you can't build >> the complete tree from clean without getting tangled up with tests. I >> propose to make more directories in the top level to contain the >> common test classes that are currently in the test-jars. This is two >> new dirs, one for math and one for core. >> >> Do people want prior review of this on a JIRA? > >
