I think I general use case for ordered dependencies is when you need two different versions of one dependency for compilation. For example I have some utility project that provides functionality for framework A. My utility project can be used with version 1.x of A and 2.x - as A changed incompatible from 1.x to 2.x and as I don't want to split my project into different versions, I need some classes of 1.x and some of 2.x for compilation. In this case the ordering is important.
Now, unfortunately, this scenario is not going to work with m2 directly as m2 only allows one version of a dependency in the classpath :( Carsten Nigel Magnay wrote: > The artifact being generated is effectively a merge of several other > artifacts of the same type - a WAR file. It's important to get the > ordering right as the overwriting precidence matters. > > I was just thinking of needing an extra bit of user data, much like > the properties you could put on dependencies in M1 that controlled > things like whether the file got included in the manifest or not; a > 'proper' ordering of all dependencies does sound harder (and maybe too > hard to be always right in all circumstances..) > > On 11/14/05, Brett Porter <[EMAIL PROTECTED]> wrote: > >>Can you describe what the relevance of the ordering is? There might be >>something already available. >> >>The suggestion of this tag is tricky, as how does dependencies brought >>in transitively get ordered? >> -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
