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 On Do, 31.03.2005, 14:16, Nicolas Chalumeau sagte: > 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, > [snip] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
