Adrian,
Sorry, I was a bit too quick with my response. In fact what I do is I have a
master project.xml that I place in the folder where I've installed Maven.
All my applications extend this POM in the following way:
<extend>${maven.home}/project.xml</extend>
Application modules will further extend the application POM like this:
<extend>${application.home}/project.xml</extend>
Within project.properties you set the correct path (which is used by
multiproject)
application.home=../../.. [or whatever path that's fit for your module]
Now when you want to build a module in isolation, whithout having the
application pom checked out, you can refer dynamically replace the
application POM with the master pom:
maven jar:install -Dapplication.home='${maven.home}'
Does this make sense?
On 5/8/05, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> On 5/9/05, Adrian Herscu <[EMAIL PROTECTED]> wrote:
> > Brett, just asked if I can use the "multiproject" goals when the
> > sub-projects are not using the <extend> mechanism - will Maven
> > build them?
>
> Yes, multiproject is unaware of what you are extending. In m1, it is
> sometimes impossible to have your "master" build match your "parent"
> build (eg, maven-plugins extends ../plugin-parent/project.xml instead
> of project.xml, but still builds with multiproject).
>
> > What do you thing about Thomas' solution? (previous post in this
> > thread)
>
> I didn't quite understand it either (but it is early ;) Seems it
> didn't work out for you though.
>
> - Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
