Eric, I'm not sure if you can break a task in small parts (never done that). However, I don't understand why you need to break the <cactus> tag in several parts rather than have a single jelly tag wrapping it. I don't see a use case for that in the current features supports by the Cactus plugin.
Thanks -Vincent > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: 10 July 2003 17:30 > To: [EMAIL PROTECTED] > Subject: RE: cvs commit: maven/src/plugins-build/cactus plugin.jelly > > The Plexus plugin was a great example, and I can see how using tags is > going > to be helpful in lots of areas.. > > Now, here is my current question. Becasue the <cactus> target is an Ant > task with various embedded tasks, I wanted to take some of the common > ones, > like <containerset> and put them in their own tags. That way I can > customize the various elements of the <cactus> target, but share all the > common code. However, when I did this: > <define:taglib uri="cactustag"> > <define:tag name="containerset"> > <ant:echo message="\n\nHERE WE ARE!\n\n"/> > <ant:echo message="val:${cactus.home.tomcat4x}"/> > <containerset> > <tomcat4x if="cactus.home.tomcat4x" > dir="${cactus.home.tomcat4x}" port="${cactus.port}" > output="${cactus.reports.dir}/tomcat4x.out" > todir="${cactus.reports.dir}/tomcat4x"> > </tomcat4x> > </containerset> > </define:tag> > </define:taglib> > > The "HERE WE ARE" message comes out, but the <cactus> tag acts as if the > <containerset> tag was never added. Is this a limitation in that my > attempting to load the <containerset> via <cactustag:containerset> won't > work? > > Eric --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
