I was just looking at that and thinking that was probably the way I
should do it.. just seemed a shame that I couldn't attach some
arbitary property inside the dependency tag, but it's no biggie.
Nigel
On 11/14/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> Right - transitivity defeats the ability to do this.
>
> What you need to do is specify the order in configuration to your
> plugin (and still declare the dependencies normally).
>
> <wars>
> <war>groupId:artifactId1</war>
> <war>groupId:artifactId2</war>
> </wars>
>
> From this you can construct an artifact filter pretty easily and
> filter the ${project.artifacts}. This is how the assembly plugin
> works.
>
> - Brett
>
> On 11/14/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]
