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]
