Sorry so late getting back on this. I'm responding on the Maven list, as this deals with the Cactus Plugin, and project organization, and may be of interest to others.
You mentioned: > - Have separate projects for each J2EE module (EJB-JAR, WAR, RAR, simple > jar libraries) Done. I'm assuming the Cactus tests (for each module) go in these projects. > - Have a project for the application (EAR in most cases) which is the > aggregation of the different J2EE module projects Done. > - (optional) Have a project for the container holding the application > (this project will contain the container's configuration files) I assume this is for stuff like jboss.xml file, etc. I skipped this as I'm using XDoclet to generate those files in the specific projects. > I would run the cactus tests in the container project as Cactus tests > run in a running container. If I understand correctly, this is different than the optional step above. This project would be a stand alone war file that will actually run the Cactus test? When running cactus:test, It runs the tests in the specified container (specified in the build.properties file?). For example, I've set cactus.home.jboss3x, so it should run using that container? Thanks again for your help. -- Bryce Fischer <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
