You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by vm...@apache.org on 2003/02/04 09:46:29 UTC
cvs commit: jakarta-cactus/documentation/docs/xdocs/participating todo.xml
vmassol 2003/02/04 00:46:29
Modified: documentation/docs/xdocs/participating todo.xml
Log:
Removed todo that are implemented :-)
Revision Changes Path
1.5 +0 -9 jakarta-cactus/documentation/docs/xdocs/participating/todo.xml
Index: todo.xml
===================================================================
RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/participating/todo.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- todo.xml 28 Jan 2003 14:55:43 -0000 1.4
+++ todo.xml 4 Feb 2003 08:46:28 -0000 1.5
@@ -180,15 +180,6 @@
Provide a full servlet container test suite a la Watchdog using Cactus
</action>
<action>
- Improve Cactus usability by providing different Cactus front ends
- that does all the packaging of the application by simply specifying
- source location, resource location and web.xml. These front ends would
- already contains all the logic to create the war and deploy it
- for a given application server. Possibilies are: Cactus standalone
- application which uses the JUnit Swing TestRunner, Cactus Ant tasks,
- Generic Cactus plugin for IDEs, Special Cactus plugin for Eclipse.
- </action>
- <action>
Ability to write Cactus tests by extending normal JUnit TestCase
instead of Cactus extensions (by using special Cactus TestSuite
objects). This will allow to easily execute the same test outside and
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org