On 28 Jun 07, at 11:48 AM 28 Jun 07, Mark Hobson wrote:
On 28/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I thought we agreed that this was not to surface in a POM? If you put
that in there now people will start using it. I thought you were
going to be able to do this strictly by changes to your installation?
The initial way I got this working was by modifying the installation
to override components.xml. I then looked again at MNG-2771 and tried
to achieve the same via a POM extension, but after chatting to Kenney
we concluded that this doesn't work in 2.0.x nor 2.1 yet, so I added
it0124 to show this. Brett then suggested using a POM property to
make the conflict resolver configuration project-specific, which is
what I've just done.
If this exposes too much then I'm happy to cut it back down to an
installation modification for now.
As long as you track this in your proposal and end result amounts to
what this is going to look like in a v4 POM in 2.1 where hopefully
we'll have something nicer like:
<conflictResolvers>
<conflictResolver>x</conflictResolver>
<conflictResolver>y</conflictResolver>
<conflictResolver>z</conflictResolver>
</conflictResolver>
And then in 2.1 if these strategies are employed we can look for the
property and map it into the POM before the build plan is executed.
Even though a graph will be used I don't think the identifiers
describing the strategy would need to change. So if this winds up
getting exposed in the POM lets pick some meaningful understandable
names before you put this in finally as if this goes in the POMs the
ids for the strategies at the very least should remain the same.
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
