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/02/25 00:42:58 UTC

[maven-bug] New comment: (MAVEN-284) Fixes for Cactus Plugin to not be tomcat specific

The following comment has been added to this issue:

     Author: David Eric Pugh
    Created: Mon, 24 Feb 2003 5:42 PM
       Body:
I tried to delete the extra patch that was rejected for being too old, but don't have permissions.  The patch file is the newer one, cactusfinal.patch.
---------------------------------------------------------------------
View the issue:

  http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-284


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-284
    Summary: Fixes for Cactus Plugin to not be tomcat specific
       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: Tue, 18 Feb 2003 10:58 AM
    Updated: Mon, 24 Feb 2003 5:19 PM
Environment: This plugin was written against both beta-8 and the cvs beta-9 dev versions.

Description:
This patch file makes the existing cactus plugin actually work.  Removes a bunch of crufty stuff (like setting a maven.cactus.container) and fixing lots of bugs.

Now you can do maven cactus:test and have it work!  Also, revamped the maven:single goal to work much better.  Don't have to start the site in a seperate thread.

Remaining Stuff:
1) Mergine web.xmls needs to be done.
2) Figure out how to provide a custom server.xml for testing.
3) Work on the deploy into a running container.
4) Figure out running reports.

I would like the patch applied as soon as possible as quite a few people have contacted me asking when the plugin would be working!


---------------------------------------------------------------------
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