One good this is to have in-container tests : look at cactus (jakarat.apache.org/cactus), it allow you to run the test in multiple server.
A great pdf talk about a possible structuration (it's not the "unique" one) : http://www.pivolis.com/pdf/J2EE_projects_Maven_V1.1.pdf Nicolas, On Wed, 30 Mar 2005 17:16:04 +0200, Georg K�ster <[EMAIL PROTECTED]> wrote: > Hello! > > First of all I want to thank this community for this wonderful tool. > Declaration of the dependencies and standardization is necessary to > manage ever growing complexity. > > Common problems occur when multiple application servers (or even > multiple releases of a single appserver) are targeted: > - jars coming with the server change/are added/move (for example > servlet-api.jar of jboss) > - deployment descriptors need to be adapted and xdoclet parameterized > accordingly > > The question arising is: how can maven help under these conditions? Do I > really need to have special versions of the project.xml for every server? > I saw some previous threads on the subject: > > http://marc.theaimsgroup.com/?l=turbine-maven-user&m=105380442001158&w=2 > http://marc.theaimsgroup.com/?l=turbine-maven-user&m=108594807801677&w=2 > > But answers where not very promising/absent. > Has the situation changed? > Are there any experiences? > > Thanks in advance! > > Georg K�ster > > --------------------------------------------------------------------- > 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]
