DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24633>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24633 add cactus:start-[debug-]server goal Summary: add cactus:start-[debug-]server goal Product: Cactus Version: Nightly Build Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Maven Integration AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] It would be good to have a goal that can start the server used to run the cactus tests in maven cactus:test, possibly in debug mode. This can hold the server open until it is ctrl-C'd, perhaps. This way, the browser servlet test runner can be used, but more importantly you can hook up your IDE to debug a remote instance, rather than have the IDE run the server. I'm not sure how to deal with multiple server configurations - whether only one should be started (controlled by properties), or if all should be started by using jelly threads to separate them. Some of the maven appserver:* goals might be reusable here - at least for Tomcat support. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
