Yes, that is what I am suggesting. It gives even finer granularity than a testuite per module and does not require moving the code back the modules.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 19, 2002 5:27 PM Subject: Re: [JBoss-dev] Build System... any ideas > > So are you suggesting that there be, more or less, a build file per > testsuite directory (e.g. org/jboss/test/jmx gets a build.xml)? Then the > testsuite/build.xml calls each of them? > > I think that would accomplish essentially the same thing I was suggesting > with the generic targets for "run xdoclet in one directory" and "build jars > from one directory" suggestion. Smaller build files might be easier to > understand individually, but might also be significantly slower. > > The ant 1.5.1 include task might help, we could include the specific > xdoclet and jar targets from small build files while keeping a single > global javac task. > > david jencks ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
