On 13/08/2008, at 12:31 PM, Oleg Gusakov wrote:
Current implementation (let's call it 2.0) is promiscuous inside the "dirty" dependency tree - all possible versions before conflict resolution. But for plugins - the first plugin found wins. I would say - we should be consistent and *treat plugins the same as dependencies*.
Agreed they should be the same. I assume by dirty you mean the one with ranges - but once resolved this can actually be made concrete - for both deps and plugins - so that releases will be reproducible.
- Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
