Reading that, I initially thought that only make a difference if B is reimplementing a class already defined in D or E (probably not a good idea, but...). In that case when I run A I would prefer to use the implementation of B rather than the one of D or E.
Now, I guess that if you are asking that, that's because in OSGi the modules are loaded in the order in which they appear. So, D and E must be loaded before. Am I right? Note that buildlist will order the module as you are asking. But can't probably use that to solve your problem. Gilles > -----Original Message----- > From: Andy Piper [mailto:[EMAIL PROTECTED] > Sent: mercredi 31 octobre 2007 11:07 > To: [email protected] > Subject: Ordering of ivy:cachepath > > I am using ivy to run tests involving OSGi bundles. In OSGi the > ordering of bundles is important at resolution time so I am using the > following: > > <ivy:cachepath conf="bundles" pathid="bundles.path.id"/> > > to generate a list of bundles in dependency order. This works ok, but > I have this problem where the dependencies are ordered *after* the > thing depending on them. So given: > > A -> B, C > B -> D, E > > The ordering in the cache path for A will be: > > B, D, E, C > > when actually what I want is: > > D, E, B, C > > Any ideas how I fix this? Shouldn't the ordering in general be what I > want rather than what is currently implemented? > > 2.0 alpha 2 > > Thanks! > > andy > > > > Notice: This email message, together with any attachments, may contain > information of BEA > Systems, Inc., its subsidiaries and affiliated entities, that may be > confidential, > proprietary, copyrighted and/or legally privileged, and is intended solely > for the use of the > individual or entity named in this message. If you are not the intended > recipient, and have > received this message in error, please immediately return this by email and > then delete it.
