> -----Original Message-----
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 03, 2004 8:11 AM
> To: 'Maven Developers List'
> Subject: RE: [site&multiproject plugins] - reorganization of goals use
> to generate sites
>
>
>
>
> > -----Original Message-----
> > From: Maczka Michal [mailto:[EMAIL PROTECTED]
> > Sent: mardi 2 novembre 2004 16:02
> > To: 'Maven Developers List'
> > Subject: RE: [site&multiproject plugins] - reorganization
> of goals use to
> > generate sites
>
>
[...]
> Yes, that's right, I'm not using reactor inside reactor. I
> have one level
> only. But why don't you ensure that you have only one level
> nested? That's
> what we do on our big project at work.
>
Becouse each level introduces in my case (and I think it is often a case)
natural way of grouping projects.
I very often use a "plugin" design patterns - it means that I have certain
"solutions" which can have some additonal functionaliy
added dynamically.
So I use such layout:
solutionA
pluginA
pluginB
solutionB
pluginA
pluginB
When I generate the whole site I want to have on the first level an overview
of available "solutions" and only to have a possibility of
seeing "addendums" to each of solutions from the website of particular
"solution".
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
