> For example for a typical 3-tier web application > (ui+controllers/service/data-access), will a maven-archetype-webapp suffice > for this setup, or would a multi-module project setup be more pragmatic?
If the components of the app will never be used individually anywhere else (in another project etc) then a more basic webapp approach may be ok. This simplifies things by only having 1 version to deal with and 1 module etc. Especially for people new to Maven, this is probably the most comfortable approach since it mimics what they have done previously. If there is ever a possibility that you will want to turn things into components and reuse them in another project or version some parts independently, then you might as well bite the bullet and go multi-module. This is also "the Maven way" and people here (myself included) will make your life a little bit difficult when you start talking about problems you're having with Java source files or configuring ejbs in your webapp since that is not a best practice. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
