Ok, I think I have it running. There are some warning when I run maven,
but I guess that's what you're working on.
Cargo starts the webserver now, but no tests are ran.
How can I check what's missing? Some questions are:
1. what classes does cactus look for to test? Should I sepcify a suite at
some place in the pom?
2. Where should the test classes be placed? I have some valid test classes
in WEB-INF/classes which run correctly when I execute them through the
browser
Here's the relevant part of my pom:
<plugin>
<groupId>org.apache.cactus</groupId>
<artifactId>cactus.integration.maven2</artifactId>
<version>1.8.1-SNAPSHOT</version>
<configuration>
<srcFile>
${project.build.directory}/test.war
</srcFile>
<destFile>
${project.build.directory}/${pom.artifactId}-cactified.war
</destFile>
<!--installLocally>true</installLocally-->
<mergeWebXml>
src/main/webapp/WEB-INF/cactus-web.xml
</mergeWebXml>
<libDependencies>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</
artifactId>
</dependency>
<dependency>
<groupId>httpunit</groupId>
<artifactId>httpunit</artifactId>
</dependency>
</libDependencies>
<redirectors>
<servletRedirector>
<name>ServletRedirector</name>
<mapping>/ServletRedirector</
mapping>
</servletRedirector>
<!--
<servletRedirector />
<filterRedirector>
<name>FilterRedirector</name>
<mapping>/test/filterRedirector</mapping>
</filterRedirector> -->
</redirectors>
</configuration>
<executions>
<execution>
<id>cactus-cactifywar</id>
<phase>pre-integration-test</phase>
<goals>
<goal>cactifywar</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<version>1.0-alpha-4</version>
<executions>
<execution>
<id>start-container</id>
<phase>pre-integration-test</phase>
<goals>
<goal>start</goal>
</goals>
</execution>
<execution>
<id>stop-container</id>
<phase>post-integration-test</phase>
<goals>
<goal>stop</goal>
</goals>
</execution>
</executions>
<configuration>
<wait>false</wait>
<timeout>20000</timeout>
<container>
<containerId>tomcat5x</containerId>
<log>target/cargo.log</log>
<output>target/output.log</output>
<zipUrlInstaller>
<url>
http://apache.speedbone.de/tomcat/tomcat-5/v5.5.25
/bin/apache-tomcat-5.5.25.zip
</url>
<installDir>${basedir}/install</
installDir>
</zipUrlInstaller>
</container>
<configuration>
<deployables>
<deployable>
<!--groupId>org.apache.cactus</groupId>
<artifactId>cactus.samples.servlet</artifactId-->
<!--location>target/samples-servlet-1.8.0-SNAPSHOT-cactified.war</location-->
<location>
${project.build.directory}/${pom.artifactId}-cactified.war
</location>
<type>war</type>
<properties>
<context>/test</
context>
</properties>
<pingURL>
http://localhost:8080/test
</pingURL>
</deployable>
</deployables>
</configuration>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<skip>true</skip>
</configuration>
<executions>
<execution>
<id>surefire-it</id>
<phase>integration-test</phase>
<goals>
<goal>test</goal>
</goals>
<configuration>
<skip>false</skip>
<systemProperties>
<property>
<name>
cactus.contextURL</name>
<value>
http://localhost:8080/test/
</value>
</property>
</systemProperties>
</configuration>
</execution>
</executions>
</plugin>
regards,
Bo
(b.t.w. <systemProperties>
<property>
<name>
cactus.contextURL</name>
<value>
http://localhost:8080/handelskantoor/
</value>
</property>
</systemProperties>
as stated on the website doesn't seem to work, I had to put a
cactus.properties file in WEB-INF/classes)
"Petar Tahchiev"
<[EMAIL PROTECTED]
l.com> Para
"Cactus Users List"
22/09/2008 15:05 <cactus-user@jakarta.apache.org>
cc
Por favor, Asunto
responda a Re: cactus 1.8.1
"Cactus Users
List"
<[EMAIL PROTECTED]
rta.apache.org>
Hi,
we are currently working on the Maven2 mojos, and I expect them to be
ready by the end of the month or at the beginning of October.
Can you try to make the servlet samples work with Maven2?
It should be pretty stright-forward: just navigate to /samples/servlet and
execute mvn clean install
After that you can see how things work their, and try to make it work for
yourself.
Thanks, Petar.
2008/9/22, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>
>
>
>
>
> Hello,
>
> I'd like to use cactus with maven 2. The documentation states that for
> this I'd need cactus 1.8.1
> I could only find 1.8.1-snapshot in svn, so I'm trying to build it.
> However, I'm getting the following error:
>
> [INFO] Using version: 2.0 of plugin:
> org.apache.maven.plugins:maven-changes-plugin
> org.apache.maven.lifecycle.LifecycleSpecificationException:
>
> No lifecycle phase binding can be found for goal: announcement-generate,
> specified as a part of the execution: announcement-generatein plugin:
> org.apache.maven.plugins:maven-changes-plugin
>
> This plugin was resolved successfully.
> However, the mojo metadata it contains does not specify a default
lifecycle
> phase binding.
>
> Please provide a valid <phase/> specification for execution:
> announcement-generate
> in plugin: org.apache.maven.plugins:maven-changes-plugin
>
>
> at
>
>
org.apache.maven.lifecycle.binding.DefaultLifecycleBindingManager.getProjectCustomBindings(
> DefaultLifecycleBindingManager.java:266)
> at
>
>
org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan_aroundBody0(
> DefaultBuildPlanner.java:99)
> at
>
>
org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan_aroundBody1$advice(
> DefaultBuildPlanner.java:403)
> at
> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan(
> DefaultBuildPlanner.java:1)
> at
>
>
org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlan(
> DefaultBuildPlanner.java:67)
> at
>
>
org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructInitialProjectBuildPlans(
> DefaultBuildPlanner.java:56)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> DefaultLifecycleExecutor.java:138)
> at org.apache.maven.DefaultMaven.execute_aroundBody0(
> DefaultMaven.java:223)
> at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(
> DefaultMaven.java:304)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
> at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(
> MavenEmbedder.java:903)
> at
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(
> MavenEmbedder.java:304)
> at org.apache.maven.embedder.MavenEmbedder.execute(
> MavenEmbedder.java:1)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
>
> Is this a known problem? Is there a workaround for this?
>
> Regards,
> Bo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Regards, Petar!
Karlovo, Bulgaria.
- - - - - - - -
| Author @ Manning Publications.
| Technical Consultant @ HP
| BGJUG-Bulgarian Java User Group Leader.
| Apache Jakarta PMC member.
| Jakarta Cactus Lead Developer.
| Blogger: http://weblogs.java.net/blog/paranoiabla/
- - - - - - - -
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
