Thanks for the quick answer. Is there sth like versioning in planning? Meaning if I contribute two "identical" (relating to the module id) modules with different versions, that hivemind uses the newer one. Or maybe a more sophisticated method of choosing the "right" version. Sth on the lines of a service (should be a kind of bootstrap service, e.g. one that is eagerloaded) that gets the information for making that decision?
Greets, Christian. > -----Ursprüngliche Nachricht----- > Von: Knut Wannheden [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 1. Dezember 2005 10:00 > An: [email protected] > Betreff: Re: module version > > > Hi Christian, > > On 12/1/05, Domsch, Christian <[EMAIL PROTECTED]> wrote: > > Hi all. > > > > I have a simple question: is the version attribute inside a > module element > > used? And if so, whatfor? The descriptor reference on the > website doesn't > > say anything about the usage of this attribute and I didn't > dig into the > > source code yet. > > > > There is actually a <dependency> element which uses it. You can use > the <dependency> element to declare a dependency upon another module. > <dependency> has an optional "version" attribute which if specified > has to match up with the version of the required module. Without the > "version" attribute specified on <dependency> any version of the > required module will satisfy the dependency. > > We hope to add more sophisticated version matching policies > in the future. > > HTH, > > --knut > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
