Ok, this was a bit hard to grasp in mail, so Jason, John and I went
through it on IRC a bit. Here are some things we arrived at. I'm being
deliberately verbose and breaking it down point by point. This is all
just best practice that we want to ensure the plugins can facilitate - I
think there a nu
I think this is a move in the right direction, in a more general sense.
It's time we thought of dependencies in a more abstract way, I think.
Rather than talking about them as purely code dependencies, I think it's
important to think of them as things that the project needs in order to
build, w
me.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 07, 2006 1:24 AM
To: Maven Developers List
Subject: Parent vs dependency aggregation, including sites and reports
Hi folks,
This is pretty important to start punting around as I need to lock in a
I prefer aggregation vs inheritance.
What about deploying the sites to the repo as type "site" and then
from the aggregated site depend on them and make the aggregated site?
On 2/6/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> This is pretty important to start punting around as I ne
Hi folks,
This is pretty important to start punting around as I need to lock in a
best practice that works on Maven 2.0 and can be used in the site
plug-in release. Please give this a review as soon as possible.
I am battling the age old question where we have parent as inheritance
and parent as
