Can someone provide an example of using the cactus plugin in a multiproject environment?
I have a project that is laid out roughly as: Root --ui (for war) --ejb (for ejb jar) --src --ejb --test-cactus --webapp --web.xml (skeleton web.xml for cactus as in samples) --ear (for final ear) The problem is that when the cactus:test-ear is run it tries to create a war that has pretty much all the files from the ejb module even though they should not be in the war. That causes an error in the deployment. The same thing seems to happen in jakarta-cactus\integration\maven\samples\ejb When I do a maven cactus:test-ear from there it seems to do the same thing (although I had to change the j2ee dependency to the jboss-j2ee to test). It causes errors such as: 00:03:42,712 INFO [Engine] StandardHost[localhost]: MAPPING configuration error for request URI /maven-cactus-sample-ejb/ServletRedirector 00:03:43,253 INFO [Engine] StandardHost[localhost]: MAPPING configuration error for request URI /maven-cactus-sample-ejb/ServletRedirector To appear in the log repeatedly. For the sample it's okay because eventually it will run.. But for my own tests it will timeout before ever getting a chance to run. :( I'm using the latest one from cvs when getting these. -Tim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
