Hi Eric,
I have committed the code in the cactus plugin that automatically discover test classes. Could you give it a try to see if it works for you? Thanks -Vincent -----Original Message----- From: [EMAIL PROTECTED] [mailto:EPugh@;upstate.com] Sent: 08 November 2002 15:41 To: [EMAIL PROTECTED] Subject: [PATCH] Allow Cactus testcases to be configurable Attached is a patch file that allows you to specify what classes to include/exlcude. By default, all classes are included, which preserves backwards compatability. This solves my issue where I have support classes in my cactus directory that I don't want run. Eric -----Original Message----- From: James Taylor [mailto:jtaylor@;4lane.com] Sent: Friday, November 08, 2002 10:35 AM To: Turbine Maven Developers List Subject: Re: DVSL replacement > I'm not sure how the performances/behaviours would differ, though at least > Jelly would reduce the dependency list & code that gets loaded. Though maybe > the quickest thing would be XSLT? > > (ducks-possible-XSLT--flames) I believe the key argument for Jelly/JSL over XSLT is that we need access to data from the POM -- of course, there are other ways we could get that information into the results, but the current DVSL accesses it directly. -- To unsubscribe, e-mail: <mailto:turbine-maven-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-maven-dev-help@;jakarta.apache.org>
