Reading through, that sounds like this would work, but unfortunately it did not
:-(
Here is in detail the items I'm setting related to cactus.
*build.properties:
==================
cactus.home.jboss3x = c:/jboss/jboss-3.2.4
# this is no longer needed, defaulted
# cactus.src.mergewebxml = ${basedir}/src/conf/cactus-web.xml
==================
*project.properties:
==================
# -------------------------------------------------------------------
# Cactus Unit Test Properties
# --comment out all, using defaults--
# -------------------------------------------------------------------
# cactus.ear=${basedir}/target/${pom.artifactId}-cactus.ear
# cactus.war.dir=${basedir}/target
# cactus.war.name=${pom.artifactId}-cactus.war
==================
*project.xml
==================
<!-- Add Clover Report support to Cactus test -->
<dependency>
<groupId>clover</groupId>
<artifactId>clover-ant</artifactId>
<version>1.3_01</version>
<properties>
<cactus.bundle>true</cactus.bundle>
</properties>
</dependency>
<dependency>
<groupId>clover</groupId>
<artifactId>clover</artifactId>
<version>1.2.3</version>
<properties>
<cactus.bundle>true</cactus.bundle>
</properties>
</dependency>
.....
<!-- note, sometimes better results if copy all java and generated
xdoclet files to one location and point sourcedirectory there-->
<sourceDirectory>src/java</sourceDirectory>
<unitTestSourceDirectory>src/test</unitTestSourceDirectory>
<integrationUnitTestSourceDirectory>src/test-cactus</integrationUnitTestSourceDirectory>
.....
<reports>
<report>maven-changes-plugin</report>
<report>maven-jdepend-plugin</report>
<report>maven-pmd-plugin</report>
<report>maven-checkstyle-plugin</report>
<report>maven-cactus-plugin</report>
<report>maven-junit-report-plugin</report>
<!--report>maven-clover-plugin</report-->
<report>maven-javadoc-plugin</report>
<report>maven-dashboard-plugin</report>
</reports>
==================
*maven.xml
==================
<preGoal name="cactus">
<attainGoal name="clover:on"/>
</preGoal>
<postGoal name="cactus">
<attainGoal name="clover:report"/>
</postGoal>
<preGoal name="war:webapp">
<attainGoal name="mycactuswar"/>
</preGoal>
<!--this is from some older e-mails/conversations-->
<goal name="mycactuswar">
<taskdef name="webdoclet" classname="xdoclet.modules.web.WebDocletTask">
<classpath>
<path refid="maven.dependency.classpath"/>
</classpath>
</taskdef>
<webdoclet
destdir="${basedir}/target/${pom.artifactId}/WEB-INF"
force="true" >
<fileset dir="${basedir}/src/test-cactus">
<include name="**/*.java" />
</fileset>
<deploymentdescriptor
distributable="false"
servletspec="2.3"
destdir="${basedir}/target/${pom.artifactId}/WEB-INF"
/>
<jbosswebxml
destdir="${basedir}/target/${pom.artifactId}/WEB-INF"/>
</webdoclet>
</goal>
==================
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 19, 2004 4:39 AM
> To: Cactus Users List
> Subject: RE: R�f. : RE: Clovering Cactus tests with Maven
>
>
> I reread the message. In fact you want to have cactus report
> and clover
> report when you call maven site:generate.
> In that case, you just have to add a preGoal on cactus who does the
> clover:on and a postGoal on cactus who does the clover:report.
> In your project.xml add the cactus report but not the clover one.
>
> This solution is not very good because the clover report will
> be done for
> all your cactus test.
> So I thing the best method is to generate the clover report
> before calling
> the site:generate (no clean between this 2 step ;) ) and
> don't include the
> clover report in your pom (just add an link in your
> navigation.xml that
> point on it).
>
> Nicolas,
>
>
>
>
>
> "Vincent Massol" <[EMAIL PROTECTED]>
> 18/11/2004 18:59
> Veuillez r�pondre � "Cactus Users List"
>
>
> Pour : "'Cactus Users List'" <[EMAIL PROTECTED]>
> cc :
> Objet : RE: R�f. : RE: Clovering Cactus tests with Maven
>
>
> Yes, that's right. You need the clover:report part
>
> -Vincent
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> > trelaze.com]
> > Sent: jeudi 18 novembre 2004 16:31
> > To: Cactus Users List
> > Subject: R�f. : RE: Clovering Cactus tests with Maven
> >
> > If my memory is good it was disgust before on the list.
> > I think you have to do something like for generating the
> clover report:
> > maven clover:on cactus clover:report
> >
> > Nicolas
> >
> >
> >
> >
> >
> > "Darren Hartford" <[EMAIL PROTECTED]>
> > 18/11/2004 16:24
> > Veuillez r�pondre � "Cactus Users List"
> >
> >
> > Pour : "Cactus Users List" <[EMAIL PROTECTED]>
> > cc :
> > Objet : RE: Clovering Cactus tests with Maven
> >
> >
> > Hey all,
> > Trying to get Clover reports on some Cactus tests. I caught the
> question
> > about clover with test-ear, but I'm not that far (yet).
> >
> > In just trying to follow some previous directions (below),
> I'm running
> > Maven-1.0.1 release (which has the Clover-1.6 plugin) and
> cactus-1.7dev.
> >
> > Following the directions, when I run "maven clover:report",
> the clover
> > plugin errors saying you need to run 'clover-setup' first.
> Well, that's
> a
> > clover problem, but still a show-stopper for step-by-step execution.
> >
> > Moving foward, doing something like "maven clover:on site"
> to do it all
> at
> > once with the clover-report-plugin in the maven POM goes
> through. The
> > Cactus tests are run and I see the results, the
> cactus-report comes out
> > fine, but a clover report is never created (I don't have any Junit
> tests,
> > just Cactus).
> >
> > ====snip====
> > [cactus] Testcase: blah1 took 0.515 sec
> > [cactus] Testcase: blah2 took 0.031 sec
> > [cactus] Shutdown message has been posted to the server.
> > [cactus] Server shutdown may take a while - check logfiles for
> > completion
> >
> > .....
> >
> > [echo] Generating the Clover...
> > maven-clover-plugin:report:
> > clover:test:
> > [echo] No tests to run Clover on
> >
> > clover:init:
> > Overriding previous definition of reference to clover.classpath
> >
> > clover:report:
> > clover:html-report-internal:
> > [clover-report] Clover Version 1.3_01, built on July 09 2004
> > [clover-report] loaded from: C:\Documents and
> > Settings\dhartford\.maven\repo
> > sitory\clover\jars\clover-ant-1.3_01.jar
> > [clover-report] No coverage data found for
> > 'C:\projects\cpams\cpamsserver3\e
> > jb_session\target\clover\database\clover_coverage.db'.
> > [clover-report] No coverage recordings found. No report will be
> > generated.
> > ===end snip====
> >
> > My code is compiled/inspected with Clover, and I see all
> the classes in
> > /target/clover/classes (minus the cactus-tests), so at
> least that part
> is
> > working. Beyond that, I'm not sure what next to check.
> >
> > -D
> >
> > > -----Original Message-----
> > > From: Vincent Massol [mailto:[EMAIL PROTECTED]
> > > Sent: Friday, July 16, 2004 7:18 AM
> > > To: 'Maven Users List'
> > > Cc: 'Cactus Users List'
> > > Subject: [Summary] Clovering Cactus tests with Maven
> > >
> > >
> > > Hi,
> > >
> > > Some of you asked how to run Clover on Cactus tests. I tried
> > > to do it and
> > > found that indeed there were some issues. I've now modified
> > > the Maven Clover
> > > plugin so that it is possible to Clover Cactus tests.
> > >
> > > You'll need to do the following:
> > >
> > > 1/ Use at least version 1.6 of the Maven Clover report. ATM,
> > > it is not yet
> > > released so you'll have to build it from the source (CVS HEAD on
> > > maven-plugins module).
> > >
> > > 2/ In the Maven project used to execute the Cactus tests, add
> > > a dependency
> > > to Clover:
> > >
> > > <dependency>
> > > <groupId>clover</groupId>
> > > <artifactId>clover-ant</artifactId>
> > > <version>1.3_01</version>
> > > <properties>
> > > <cactus.bundle>true</cactus.bundle>
> > > </properties>
> > > </dependency>
> > >
> > > 3/ Then type "maven clean clover:on cactus". This
> instruments both the
> > > project's source code + its Cactus tests
> > >
> > > 4/ Once it is finished, type "maven clover:report" to
> > > generate the HTML
> > > Clover report. It will be located in target/docs/clover/index.html
> > >
> > > -Vincent
> > >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
