fix for running tests with cactus:test-ear (already known?)

[Mark Slater <ma...@analogsoftware.com>]

This may be covered someplace already, but I didn't find it. I noticed 
that when running "maven cactus:test-ear", or "maven cactus:report" 
when "cactus.is.ear=true", none of the tests get run.

Part of my hesitation is that this is all new to me - maven, cactus, 
J2EE, etc. But what I found was that in the 
cactus-maven-1.6/plugin.jelly file, line 1101, the test-ear goal looks 
for tests using:

<ant:batchtest>
     <ant:fileset dir="${cactus.src.dir}"
         includes="${cactus.test.includes}"
         excludes="${cactus.test.excludes}"/>
</ant:batchtest>

But, when compiling, the test classes are put in 
${cactus.target.classes.dir}.

So, I changed the ant:fileset dir to:

     <ant:fileset dir="${cactus.target.classes.dir}"

And now my tests get run.

Is this something known? Or do I have my properties screwed up 
someplace else, and that's what's causing this? If this does need to be 
patched in the plugin, how do I go about doing that?

Thanks!

Mark

RE: fix for running tests with cactus:test-ear (already known?)

[Vincent Massol <vm...@pivolis.com>]

Hi Mark,

Not sure why you had the problem. There is a sample EJB project in
jakarta-cactus/integration/samples/ejb (in CVS) which I use to verify the
plugin works and it's been working fine for me.

That said, I've noticed that cactus:test-ear was not using the
CactusScanner, which automatically discover what Java classes are Cactus
tests. I've now modified the code in CVS.

As a consequence, it should now work fine for you.

Thanks
-Vincent

> -----Original Message-----
> From: Mark Slater [mailto:mark@analogsoftware.com]
> Sent: mercredi 9 juin 2004 01:09
> To: cactus-user@jakarta.apache.org
> Subject: fix for running tests with cactus:test-ear (already known?)
> 
> This may be covered someplace already, but I didn't find it. I noticed
> that when running "maven cactus:test-ear", or "maven cactus:report"
> when "cactus.is.ear=true", none of the tests get run.
> 
> Part of my hesitation is that this is all new to me - maven, cactus,
> J2EE, etc. But what I found was that in the
> cactus-maven-1.6/plugin.jelly file, line 1101, the test-ear goal looks
> for tests using:
> 
> <ant:batchtest>
>      <ant:fileset dir="${cactus.src.dir}"
>          includes="${cactus.test.includes}"
>          excludes="${cactus.test.excludes}"/>
> </ant:batchtest>
> 
> But, when compiling, the test classes are put in
> ${cactus.target.classes.dir}.
> 
> So, I changed the ant:fileset dir to:
> 
>      <ant:fileset dir="${cactus.target.classes.dir}"
> 
> And now my tests get run.
> 
> Is this something known? Or do I have my properties screwed up
> someplace else, and that's what's causing this? If this does need to be
> patched in the plugin, how do I go about doing that?
> 
> Thanks!
> 
> Mark
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
> 
> 
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.711 / Virus Database: 467 - Release Date: 25/06/2004
> 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.711 / Virus Database: 467 - Release Date: 25/06/2004