Hi Stephane,

Good call as it's already been fixed in CVS HEAD (bug 26811 on
bugzilla). See
http://jakarta.apache.org/cactus/integration/maven/changes-report.html:

        Added support for running tests packaged as an EAR when the
Cactus 
        plugin is triggered by defining the Cactus report in 
        <code>project.xml</code>.

That said, there seems to be a new problem reported by J. Joseph
Benavidez (see attached).

I'll do a nightly release of the maven plugin in the coming hours.

Thanks
-Vincent

> -----Original Message-----
> From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
> Sent: 26 February 2004 09:12
> To: [EMAIL PROTECTED]
> Subject: Cactus.execute.during.report
> 
> Hello,
> 
> I am about to fill a feature request but I want to be sure that it's
not
> yet
> implemented. We are using cactus to test our EJBs with maven. We use
the
> latest 1.6dev release (the one from january).
> 
> It seems that the cactus.execute.during.report property is launching
> always
> the 'test' target (that is the one that tests stuff packaged in a
WAR). We
> don't have such testing, only test-ear is used.
> 
> Before this update we used a pregoal for the site:deploy goal. Like
this,
> cactus results are available for reporting.
> 
> Is there a way to specify the target to launch when
> cactus.execute.during.report is set to true?
> 
> Thanks,
> 
> Stephane
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

--- Begin Message ---
Title: weird xdoc reporting behavior using cactus-maven from cvs head

Hi,

I was hoping someone else could confirm this behavior... I'm trying to
run the site goal for my
maven project, and I'm seeing something weird... I've placed the
cactus-maven-reports tag
in my project.xml (I'm using the cactus, cactus-ant, and cactus-maven
code from cvs head, which
I've built to be 1.6dev-20040210)... but what I'm seeing is that when
xdoc runs, it actually generates documentation
for the cactus plugin, and not my project! Here's some sample output:

...
xdoc:jelly-transform:
    [echo] Generating
/home/jjb/.maven/plugins/cactus-maven-1.6dev-20040210/target/docs/checkstyle-report.html from /home/jjb/work/myproj/web/shared-web/target/generated-xdocs/checkstyle-report.xml

    [echo] Generating
/home/jjb/.maven/plugins/cactus-maven-1.6dev-20040210/target/docs/javadoc.html from /home/jjb/work/myproj/web/shared-web/target/generated-xdocs/javadoc.xml

    [echo] Generating
/home/jjb/.maven/plugins/cactus-maven-1.6dev-20040210/target/docs/cactus-report.html from /home/jjb/work/myproj/web/shared-web/target/generated-xdocs/cactus-report.xml

    [echo] Generating
/home/jjb/.maven/plugins/cactus-maven-1.6dev-20040210/target/docs/jdepend-report.html from /home/jjb/work/myproj/web/shared-web/target/generated-xdocs/jdepend-report.xml

...

I should be seeing something closer to this (which is what happens when
I comment out
the <maven-cactus-reports> from my project.xml):

...
xdoc:jelly-transform:
    [echo] Generating
/home/jjb/work/myproj/web/shared-web/target/docs/checkstyle-report.html
from
/home/jjb/work/myproj/web/shared-web/target/generated-xdocs/checkstyle-report.xml
    [echo] Generating
/home/jjb/work/myproj/web/shared-web/target/docs/javadoc.html from
/home/jjb/work/myproj/web/shared-web/target/generated-xdocs/javadoc.xml
    [echo] Generating
/home/jjb/work/myproj/web/shared-web/target/docs/jdepend-report.html
from
/home/jjb/work/myproj/web/shared-web/target/generated-xdocs/jdepend-report.xml
    [echo] Generating
/home/jjb/work/myproj/web/shared-web/target/docs/junit-report.html from
/home/jjb/work/myproj/web/shared-web/target/generated-xdocs/junit-report.xml
    [echo] Generating
/home/jjb/work/myproj/web/shared-web/target/docs/license.html from
/home/jjb/work/myproj/web/shared-web/target/generated-xdocs/license.xml
...


I'm using maven 1.0-rc1.

Any ideas? Is anyone seeing the same thing?

Thanks!

j.joseph


--- End Message ---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to