Hi Nicolas,
I'm still investigating this approach. Personally I'm not so sure about the following statement of yours:
> In fact it his an elegant solution as you can produce one artifact per > ear (it is the maven politic too) for each server kind/environement. > The specific goes in application and you reuse module (jar/war/...) > who are généric by definition.
The war is depending on servlet-api.jar (or alike) which cannot be included in the war. Can one really assume that one servlet-api.jar is enough for all app-servers? And furthermore, that wars are generic and really independent of application servers? I've seen strange LinkExceptions in Java ... but maybe I'm missing something?
Georg
Nicolas Chalumeau wrote:
I imagine you can ask Vincent if there was evolution since 2003 (he read this list so he can aswer...)
In fact it his an elegant solution as you can produce one artifact per ear (it is the maven politic too) for each server kind/environement. The specific goes in application and you reuse module (jar/war/...) who are généric by definition.
It is the structure I use in my compagny and using multiproject with it make that our maven.xml his "very" small.
Nicolas,
On Thu, 31 Mar 2005 12:45:50 +0200, Georg Köster <[EMAIL PROTECTED]> wrote:
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...
Georg
Nicolas Chalumeau wrote:
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]
--------------------------------------------------------------------- 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]
