But how does that help in the situation where you declare dependencies A and B, but both declare a dependency C at the same level? Is C first, second or third when ordered?
I haven't looked at this issue, but an application should avoid classpath ordering at all costs. - Brett On 11/14/05, Mark Hobson <[EMAIL PROTECTED]> wrote: > This discussion kinda overlaps with an issue I raised with the eclipse plugin: > > http://jira.codehaus.org/browse/MNG-1412 > > I think the order should be nearest first, and then the order > specified in the pom. > > Mark > > On 14/11/05, Nigel Magnay <[EMAIL PROTECTED]> 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? > > > > > > - Brett > > > > > > On 11/14/05, Nigel Magnay <[EMAIL PROTECTED]> wrote: > > > > Hi - > > > > > > > > I'm doing some processing with a custom mojo that relies on the > > > > dependency information to build an artifact, but the order of > > > > processing is important. Because MavenProject.getArtifacts() returns a > > > > set, this is unordered with respect to the pom.xml; I was wondering if > > > > it's possible to add extra information in the pom, something like > > > > > > > > ...> > > > > <dependency> > > > > <groupId>blah</groupId> > > > > <artifactId>thing</artifactId> > > > > <version>3.8.1</version> > > > > <order>1</order> <------------------ > > > > </dependency> > > > > <dependency> > > > > <groupId>woo</groupId> > > > > <artifactId>yay</artifactId> > > > > <version>3</version> > > > > <order>2</order> <------------------ > > > > </dependency> > > > > <... > > > > > > > > Is there a good way of tackling this? > > > > > > > > --------------------------------------------------------------------- > > > > 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] > > > > > > > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
