You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by bo...@werken.com on 2003/01/31 01:18:23 UTC
[maven-bug] New comment: (MAVEN-232) Fixes for Cactus Plugin
The following comment has been added to this issue:
Author: David Eric Pugh
Created: Thu, 30 Jan 2003 6:18 PM
Body:
Victory is almost mine.. I solved the formatting of the reports. I have a workaround for not dynamically merging the web.xml's. All the little changes like pom.id -> pom.artifactID are tied in. At this point though there are some issues with it:
1) The <j:thread> task doesn't seem to work. It throws a jelly exception. Therefore to run the tests you have to start one window to start up tomcat, and the other to run the tests.
Window 1: maven test:cactus (Starts up Tomcat)
Window 2: maven test:cactus (Runs the tests)
2) The importing of scripts (tomcat.4x.jelly) works, but the only way to call the goals is from a goal in plugin.jelly. Therefore, added the cactus:test goal that then calls cactus:test-{maven.cactus.container}. However, this led to another issue, which was an included goal in the tomcat.4x.jelly could not call attainGoal of another goal (or something crazy like that).
So therefore some of the code in tomcat.4x.jelly was pulled into plugin.jelly.
At this point though, the plugin is now usable, and prior to this effort the plugin was totally broken. So I would really like my changes committed.
---------------------------------------------------------------------
View the issue:
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-232
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-232
Summary: Fixes for Cactus Plugin
Type: Bug
Status: Assigned
Priority: Major
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Component: plugin-cactus
Versions:
1.0-beta-8
Assignee: Jason van Zyl
Reporter: David Eric Pugh
Created: Thu, 30 Jan 2003 2:29 PM
Updated: Thu, 30 Jan 2003 2:29 PM
Environment: Win2k, CVS Head
Description:
I have fixed a bunch of the small things that are preventing the cactus plugin from working. The big things preventing it from working are:
1) Dynamic include of scripts for dynamic goals. Goals don't show up.
2) Starting of Tomcat seems to just hang..
3) web.xml and reports are currently in dvsl. They need to be moved to jsl.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.werken.com/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
Re: [maven-bug] New comment: (MAVEN-232) Fixes for Cactus Plugin
Posted by di...@multitask.com.au.
bob@werken.com wrote on 31/01/2003 11:18:23 AM:
> 1) The <j:thread> task doesn't seem to work. It throws a jelly
> exception. Therefore to run the tests you have to start one window
> to start up tomcat, and the other to run the tests.
> Window 1: maven test:cactus (Starts up Tomcat)
> Window 2: maven test:cactus (Runs the tests)
Can you post a stacktrace or something so I can help fix this?
> 2) The importing of scripts (tomcat.4x.jelly) works, but the only
> way to call the goals is from a goal in plugin.jelly. Therefore,
> added the cactus:test goal that then calls cactus:test-{maven.
> cactus.container}. However, this led to another issue, which was an
> included goal in the tomcat.4x.jelly could not call attainGoal of
> another goal (or something crazy like that).
> So therefore some of the code in tomcat.4x.jelly was pulled into
plugin.jelly.
>
> At this point though, the plugin is now usable, and prior to this
> effort the plugin was totally broken. So I would really like my
> changes committed.
Cool. Let me know what else I can do to help.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au