Re: Parent vs dependency aggregation, including sites and reports

2006-02-07 Thread Brett Porter
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

Re: Parent vs dependency aggregation, including sites and reports

2006-02-07 Thread John Casey
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

RE: Parent vs dependency aggregation, including sites and reports

2006-02-07 Thread Brian E. Fox
Brett, I agree with most of what you said in this mail and in your POM-Problems email. I just have this comment: >From the POM-problems email: "3) Separating inheritance of versioned and transient info A: Deprecate dependency inheritance (bare with me :) The problem of separation only seems to ap

Re: Parent vs dependency aggregation, including sites and reports

2006-02-06 Thread Carlos Sanchez
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