> -----Original Message----- > From: Peter Donald [mailto:[EMAIL PROTECTED]] > Sent: Friday, March 29, 2002 11:22 AM > To: Turbine Developers List > Subject: Re: [maven] testing set > > > On Sat, 30 Mar 2002 02:25, Jason van Zyl wrote: > > We might even be able to have a default behaviour where the > > **/*Test*.java pattern in implicit so that people don't > have to define > > <unitTestEntries> unless they want to exclude something. > > That would not work well with quite a few projects. It is > fairly common for > some projects to have both *TestCase.java and *TestSuite.java > (or TestAll) > and thius would lead to tests being executed twice. > > BTW is there any support for optional compilation/junit > stuff. ie How easy is > it to only compile certain classes if certain jars are in > Classpath and so > forth?
We were burned by allowing this in our legacy build files and hoped we would not need to repeat the mistake again. We had conditional compiling based on classes found in the classpath, but that just led to code that never got compiled. I believe we decided that code of this type would be better off in its own project, not condionally ignored. Really a preference/best practice sort of thing I guess, would this work for you? ================================================================= Jeffrey D. Brekke Quad/Graphics [EMAIL PROTECTED] http://www.qg.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
