Hi Alex, a quick example for this, see here: https://is-micro.myip.hu/trac/ismicro-commons/browser/trunk/ismicro-proximity
Three modules: px-core (j2ee and transport independent), px-core-maven (maven bindings for core, till no sign of webapp) and px-webapp. The module separation should be "natural" and/or "logical" -- whetever it means :) In my practice it means, produce ONLY ONE ARTIFACT, be as small and as simple as it can (but naturally keep the overall module count manageable). Maven generated site from these sources here: http://proximity.abstracthorizon.org/ ~t~ On 7/6/06, ben short <[EMAIL PROTECTED]> wrote:
Also have a look at the better builds with maven book, there is an example in there. On 7/6/06, ben short <[EMAIL PROTECTED]> wrote: > Create a project for each of the core module and the children. then > the webapp can pull them in as dependancies. > > On 7/6/06, Alex Shneyderman <[EMAIL PROTECTED]> wrote: > > How does one disect a web app into many modules but deploy it as one web app? > > > > This is what I mean: > > > > We have a web application that is quite big. We can identify many > > modules of it. There is a few core modules, and a bunch of child > > modules. Practically all children are dependendent on core modules, > > some child modules depend on other child modules. The modularization > > is done in purely logical way. Meaning, we still have one maven > > project for the webapp. > > > > I was wondering if anyone can suggest a way to break those modules up > > into seprate physical modules while keeping the ability to create a > > unifying webapp? Is it even possible with Maven 1 or 2? > > > > -- > > Thanks, > > Alex. > > > > --------------------------------------------------------------------- > > 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]
