The following comment has been added to this issue:
Author: Felipe Leme
Created: Wed, 8 Sep 2004 3:30 PM
Body:
Dan,
I'm not sure if your patch is ok because I applied it and now cactus is not working in
my project. Instead of running the cactifywar tasks, it only display the task on the
console, as shown below:
war:war:
[echo] Building WAR configmanager
[jar] Updating jar: S:\components\components\configmanager\target\configmana
ger-1.1.4.war
<cactifywar destfile="s:\components\components\configmanager/target/configmanage
r-cactus.war" version="2.3"><classes dir="s:\components\components\configmanager
/target/test-cactus-classes"></classes><filterredirector mapping="/test/filterRe
director.jsp"></filterredirector><classes dir="C:\Documents and Settings\t_fl01\
.maven\cache\cactus-maven-1.7dev\plugin-resources/jboss3x"><include if="cact
us.home.jboss3x" name="*.properties"></include></classes><webinf dir="C:\Documen
ts and Settings\t_fl01\.maven\cache\cactus-maven-1.7dev\plugin-resources/jbo
ss3x"><include if="cactus.home.jboss3x" name="jboss-web.xml"></include></webinf>
<lib file=""></lib></cactifywar>
cactus:test-war:
<cactus fork="yes" failureproperty="cactustests.failure" warfile="s:\components\
components\configmanager/target/configmanager-cactus.war" printsummary="withOutA
ndErr" errorproperty="cactustests.error"><classpath><pathelement path="s:\compon
ents\components\configmanager/target/classes"></pathelement><pathelement locatio
n="s:\components\components\configmanager/target/test-cactus-classes"></pathelem
ent></classpath><containerset><jboss3x config="default" output="s:\components\co
mponents\configmanager/target/test-cactus-reports/jboss3x.out" tmpdir="d:\jboss-
3.0.8_tomcat-4.0.6/server/cactus" if="cactus.home.jboss3x" todir="s:\components\
components\configmanager/target/test-cactus-reports/jboss3x" port="8080" dir="d:
\jboss-3.0.8_tomcat-4.0.6"></jboss3x><orion1x output="s:\components\components\c
onfigmanager/target/test-cactus-reports/orion1x.out" if="cactus.home.orion1x" to
dir="s:\components\components\configmanager/target/test-cactus-reports/orion1x"
port="8080" dir=""></orion1x><orion2x output="s:\components\components\configman
ager/target/test-cactus-reports/orion2x.out" if="cactus.home.orion2x" todir="s:\
components\components\configmanager/target/test-cactus-reports/orion2x" port="80
80" dir=""></orion2x><resin2x output="s:\components\components\configmanager/tar
get/test-cactus-reports/resin2x.out" if="cactus.home.resin2x" todir="s:\componen
ts\components\configmanager/target/test-cactus-reports/resin2x" port="8080" dir=
""></resin2x><resin3x output="s:\components\components\configmanager/target/test
-cactus-reports/resin3x.out" if="cactus.home.resin3x" todir="s:\components\compo
nents\configmanager/target/test-cactus-reports/resin3x" port="8080" dir=""></res
in3x><tomcat4x output="s:\components\components\configmanager/target/test-cactus
-reports/tomcat4x.out" if="cactus.home.tomcat4x" todir="s:\components\components
\configmanager/target/test-cactus-reports/tomcat4x" port="8080" dir=""></tomcat4
x><tomcat5x output="s:\components\components\configmanager/target/test-cactus-re
ports/tomcat5x.out" if="cactus.home.tomcat5x" todir="s:\components\components\co
nfigmanager/target/test-cactus-reports/tomcat5x" port="8080" dir=""></tomcat5x><
weblogic7x output="s:\components\components\configmanager/target/test-cactus-rep
orts/weblogic7x.out" if="cactus.home.weblogic7x" todir="s:\components\components
\configmanager/target/test-cactus-reports/weblogic7x" port="8080" dir=""></weblo
gic7x></containerset><formatter usefile="false" type="plain"></formatter><format
ter type="xml"></formatter> [test] [ERROR] Could not find org.apache.testlet.
engine.TextTestEngine. Make sure you have it in your classpath
</cactus>
It might be an issue in my cactus version (which I generated from CVS), but it works
fine if I use the old maven.jar.
-- Felipe
Felipe
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1087?page=comments#action_23915
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1087
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1087
Summary: Dependency type should participate in equals() and hashcode()
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: 1 hour
Time Spent: Unknown
Remaining: 1 hour
Project: maven
Components:
model
Fix Fors:
1.1
Versions:
1.0
Assignee:
Reporter: Eric Bottard
Created: Mon, 22 Dec 2003 3:48 PM
Updated: Wed, 8 Sep 2004 3:30 PM
Description:
I was trying to bundle taglibs in a war project when i stumbled into this unexpected
behavior : for each and every taglib in my web-app, either the jar file or the tld got
copied to the target web-app, but I could not get them to be copied together.
After a moment I realized that the dependency for a given taglib (one jar and one tld)
had the same artifactId but different types (jar and tld). A quick hack in the war
plugin shows that the forEach loop only sees one of the two.
So I guess that the dependency type should participate in equals() and hashcode() for
a dependency (or modify the getId() of Dependency, but I don't know the other impacts).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
