On 5/16/05, Gilles Dodinet <[EMAIL PROTECTED]> wrote: > indeed, and if using the defaults, no configuration should be needed at > all here. also in this case, using another descriptor doesn't seem to be > the way to go as it would be pretty odd : one of the primary goal is > indeed to generate/update a pde plugin descriptor.
Agreed. > last, while the dependency filtering may be a nice addition, i think > there's still a visibility issue here and in some way, doesn't it > invalidate the transitivity feature since it would require the user to > have an almost complete view on the underlying dependencies ? I see your point, but I'm not sure its a problem, or whether buried properties on the deps would help. You need to give the "end user" control of how the dep is used, so they'd need to be able to override it anyway. I don't think it's a problem as is, because again the defaults should be pretty close - so its only when you start inheriting something you don't want, you exclude it based on that at the time. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
