maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Georg Köster <>
Subject Re: Targeting multiple appservers
Date Thu, 31 Mar 2005 10:45:50 GMT
Thanks Nicolas! I imagined this easier than that, taken into 
consideration that the article dated from 2003 I hoped that something 
orthogonal to projects had been introduced to manage portability...


Nicolas Chalumeau wrote:
> One good this is to have in-container tests : look at 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) :
> Nicolas,
> On Wed, 30 Mar 2005 17:16:04 +0200, Georg Köster <> wrote:
>>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
>>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:
>>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:
>>For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message