Brett Porter wrote:
On 19/06/2008, at 11:29 AM, Dan Fabulich wrote:
Brett Porter wrote:
3.0-alpha-1: released as is, with or without those few fixes I was
looking at getting in.
3.0-alpha-X: later introduce the mercury and SAT based stuff as an
optional component
3.0: when all the above is stable and the resolution method is
selectable
Is that how everyone sees it going?
[..]
For my money, it sounds like the SAT differences will be significant
enough that we can't turn it on by default, so we have to leave the
old resolver in, so we can/should ship a 2.1 alpha without it.
Thoughts?
Yes, I agree. I think Jason put it nicely - let's focus on spending
the time getting artifact handling right (whatever the version might
be where that lands). At that time, we can either make a once only
backwards compat break or a compat mode and spend the time making sure
it's easy for people to move on to it.
Let me stress it here once again: maven-artifact-3.0-xxx has two
resolvers: the "old" one that is inherited from 2.x.x and used by the
build, and experimental "graph" resolver (very raw), that is used by
external APIs and visualization - but not by the build. SAT will replace
the "graph" resolver, and in 2.1.(2+) or 3.x.x we can make the build
configurable to use either or, so that by default the "old" be used, and
they will be able to turn SAT-based on.
Thanks,
Oleg
In the mean time, let's start getting the 2.1 alpha out, focus on
backwards compat in the current artifact handling and core, and start
exposing the new core features and stability improvements to users.
Cheers,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
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]
