> -----Original Message----- > From: Sonnek, Ryan [mailto:[EMAIL PROTECTED] > Sent: 12 June 2003 22:12 > To: 'Maven Users List' > Subject: RE: howto: cactify a project? > > Thanks for the reply! > I send my previous email about 5 seconds before yours came in. since EAR > testing is not yet available, you're suggesting that have each module > deploy > a war file for testing (mainly my EJB module). Since all of my EJB > testcases extend the ServletTestCase, this would work correctly, wouldn't > it? > > Many of the testcases I want to do with my servlet's and taglibs involve > looking up EJB's and testing that the results are correct. I also perform > tests to ensure that the EJB lookups are performed successfully. Writing > testcases JUST for the WAR module seem worthless to me if they are > deployed > without the associated EJB module. Thus EAR testing is a major necessity > for me. I would be glad to help out any way possible to integrate EAR > testing to the cactus plugin. > > =)
I'm not really saying this :-). What I'm saying is that you *cannot* currently use the Cactus plugin for Maven for tests using EJBs. This is not yet a supported use case. I'll work on that but don't expect anything soon. However, what I'm saying is that if you have an urgent need, you can always use what worked when you use Ant and put those scripts in your project's maven.xml file. Thanks -Vincent > > Ryan > > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 12, 2003 2:55 PM > To: 'Maven Users List' > Subject: RE: howto: cactify a project? > > Hi Ryan, > > > -----Original Message----- > > From: Sonnek, Ryan [mailto:[EMAIL PROTECTED] > > Sent: 12 June 2003 21:45 > > To: 'Maven Users List' > > Subject: howto: cactify a project? > > > > I recently 'mavenized' my project, breaking it up into several > subprojects > > (common, ejb, war, ear). Now, I'm trying to unit test my EJB's and > web > > projects, but I'm having extreme difficulty getting it working. How > > should > > cactus tests be run? Should there be src/test-cactus for every > subproject > > that needs testing? > > Yes > > > Does each subproject need to be deployed as a war > > file > > for cactus to test them correctly? > > The Maven plugin for Cactus currently only supports unit testing of > Servlets/Filters/Taglibs. > > You just need to type "maven cactus" and it will nicely and > automatically package the code in a war, deploy it, start the container, > run the tests, stop the container. > > Support for EAR packaging/deployment is not yet available in the Maven > plugin for Cactus. It's really easy to do with the new <cactus> task (in > Cactus 1.5), but I haven't had the time to do it yet. An example is > available at: > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/junitbook/junitbook/ejb/i > ntegration/ > > Patches are welcome :-) > > > > > I have used cactus extensively in my old build system, but since I've > > moved > > to maven (quite happily I might add), I have yet to get junit and > cactus > > tests back into my project development. > > You can still use your old way of doing things for Cactus if you want, > by putting your Ant scripts in your maven.xml file. > > However, my goal is to support all use cases in the Cactus plugin... > eventually... > > Thanks > -Vincent > > > > > Ryan > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
