On 8/9/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote:
> I like adding a pom to my Maven installation directory, share it in SCM and
> then all projects can extend from the pom added to Maven by referering to it
> as
> <extend>${maven.home}/project.xml</extend>
> I like to refer to this pom added to Maven as the program-level pom. Each
> project extends the program-level pom with an application-level pom. The
> application-level pom is then extended by module poms.
> Rgds,
> Thomas
> On 8/9/05, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> >
> > Is there a best practices for using the extend tag in the POM?
> >
> > My structure is something like:
> >
> > holder-dir
> > Project1
> > project.xml
> > Project2
> > project.xml
> > Project3
> > project.xml
> >
> > Some things are common between the projects (by convention, not by
> > using the extend). I would like to take advantage of the multiproject
> > plugin for site generation, etc.
> >
> > Have seen suggested something like:
> >
> > holder-dir
> > project.xml -- Multiproject POM
> > maven-common
> > project.xml -- Common properties
> >
> > Project1
> > project.xml
> > Project2
> > project.xml
> > Project3
> > project.xml
> >
> > Each of the Project POMs would extend the POM in maven-common.
> >
> > Any thoughts/suggestions? What successes or failures have people had
> > going this route?
> >
> > Thanks,
> > Grant
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
If you are using Eclipse, you can/should skip the
holder-dir/project.xml; just have everything extend from
maven-common/project.xml
--
Jamie Bisotti
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
