Thanks Eric for the patch. I have actually finished writing some java code to make this completely transparent for the user. The code is implemented as a Jelly tag and checks, for all files in a filesets, whether they are Cactus TestCase or not, i.e. if they extend Cactus AbstractTestCase (we might want to refine the rule in the future for checking if there are tests in the test case for example, etc).
I'm ready to test and commit it but I'm having issues with Maven/Jelly classloader and am a bit stuck (see my previous email of today named "Plugin classloader problem... help!"). As a side note, I have also written a new goal yesterday for running the test suite using the JUnit Swing Test Runner (but it needs the Jelly Tag mentioned above). Thanks again for your help. -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> � -- 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>
