My understanding was that it was all experimental at this point to
see what actually worked, then need to decide where it lands.
Requiring a change in the install is no good - it ruins the install
for general use and is more hassle than it's worth. I think the
(undocumented, unsupported) property is fine - it's just as "use at
your own risk" as dropping something into the install dir.
I've no problems with this landing on trunk and building up test
cases for the relevant uses of it to be upheld under any later
changes to the artifact mechanism.
I'm still not convinced of it landing in a 2.0.x release because it's
a new feature that won't persist in its current form (at least in the
way it's exposed). That said, I can't see how the feature would
really change in 2.1 other than, obviously, in the implementation.
You're still going to be selecting newest or nearest or whatever
against a set of graph of dependencies, and the results should be
essentially the same.
Perhaps we can maintain a branch that is 2.0.x + this patch. It's
otherwise just as stable as 2.0.x, you just have to build it from
source yourself and read the warning label on the tin.
- Brett
On 29/06/2007, at 4:48 AM, 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.
Cheers,
Mark
---------------------------------------------------------------------
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]
