Jamie McCrindle <[EMAIL PROTECTED]> wrote on 26/09/2003 07:14:04
PM:
> here's the problem:
>
> we have a main project (multiproject type project) and then a whole
bunch of
> component projects. normally, the directory structure should look
something
> like this:
>
> [parent]
> --main
> --a
> --b
>
> which means that i can just use:
>
> maven.multiproject.basedir=..
> maven.multiproject.excludes=main/project.xml
>
> for the multiproject plugin, or
>
> <maven:reactor
> basedir=".."
> includes="*/project.xml"
> excludes="main/project.xml"
>
> for my reactor.
>
> the problem is that people often have multiple versions of the component
> projects checked out (for working on production branches), which gives a
> directory structure a bit more like this:
>
> [parent]
> --main
> --a
> --a-1.4
> --b
> --b-1.2
> --b-1.3
>
> so i wanted to be a little more explicit about which projects are
included.
> which i can just do like this i guess:
>
> maven.multiproject.includes=a-1.4/project.xml,b-1.2/project.xml
Set the version of 'a' or 'b' in a property, e.g.
aVersion=1.4
bVersion=1.2
maven.multiproject.includes=a-${aVersion}/project.xml,b-${bVersion}/project.xml
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
