Great.. At any rate, since the two command windows seems to work, I'm not
too worried. However, as I dig into testing, I require a servlet to be
started so that it can hand some config data to the JSP tags that I want to
test. The servlet is started with this in the web.xml:
<!--=========== DbForms Configuration Servlet ===========-->
<servlet>
<servlet-name>org.dbforms.ConfigServlet</servlet-name>
<servlet-class>org.dbforms.ConfigServlet</servlet-class>
<init-param>
<param-name>dbformsConfig</param-name>
<param-value>/WEB-INF/conf/dbforms-config.xml</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
However, the cactus plugin uses the conf/web13.xml file. I tried to create
my own web.xml that contained everything in web13.xml plus the above servlet
mapping.. Then set in my project.propertis:
maven.cactus.webxml = ./test-cactus/web.xml
However, it still continues to use the one from the plugin's /conf
directory. Any other suggestions on the approach I should take?
Eric Pugh
-----Original Message-----
From: Vincent Massol [mailto:vmassol@;octo.com]
Sent: Tuesday, October 29, 2002 2:07 PM
To: 'Turbine Maven Developers List'
Subject: RE: Issue with Maven Cactus Plugin
Hi Eric,
It was working fine until recent changes in Maven, which for some
reasons seem to have broken it... I haven't been able to locate the
problem yet and I do not have much time ATM unfortunately :-(
I've sent an email on commons-dev in the hope that James Strachan will
help us diagnosis the problem as the NPE comes from Jelly.
Thanks
-Vincent
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:EPugh@;upstate.com]
> Sent: 29 October 2002 17:43
> To: [EMAIL PROTECTED]
> Subject: Issue with Maven Cactus Plugin
>
> Hi all,
>
> I just finished doing a successful bootstrap build of Maven from
today's
> source. I am trying out the cactus plugin, and if I run the:
> maven cactus:test-tomcat-4x
> target directly, I get this error:
> cactus:test-tomcat-4x:
> [echo] maven.cactus.tomcat4x.home = c:/java/tomcat
> cactus:tomcat-4x-run:
> [waitfor] [ERROR] org.apache.commons.jelly.JellyException:
> java.lang.NullPoi
> nterException File:
> file:/C:/java/maven/plugins/maven-cactus-plugin-1.0-SNAPSHOT
> /scripts/tomcat.4x.jelly At tag <attainGoal>: line: 57 column: 54
> [waitfor] [ERROR] at
> org.apache.commons.jelly.impl.TagScript.handleExcepti
> on(TagScript.java:604)
> [waitfor] [ERROR] at
> org.apache.commons.jelly.impl.TagScript.run(TagScript
> .java:281)
> [waitfor] [ERROR] at
> org.apache.commons.jelly.impl.ScriptBlock.run(ScriptB
> lock.java:134)
> [waitfor] [ERROR] at
> org.apache.commons.jelly.tags.core.ThreadTag$1.run(Th
> readTag.java:98)
> [waitfor] [ERROR] at java.lang.Thread.run(Thread.java:484)
>
> However, if in one commandline window I start tomcat with:
> maven cactus:start-tomcat-4x
>
> and then in another window run the
> maven cactus:test-tomcat-4x
>
> everything appears to work, and since I am using the sample cactus
test
> that
> come with the plugin, I can see everything!
>
> I looked at the jelly file, but everything looks okay...
>
> Eric Pugh
--
To unsubscribe, e-mail:
<mailto:turbine-maven-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail:
<mailto:turbine-maven-dev-help@;jakarta.apache.org>
