I would like to see this additional requirement too.
--
Trygve
Kenney Westerhof wrote:
Yup, I agree.
but still the case where 2 matches are equally near should be solved;
I think atm. this is either random or first/last-encountered-wins; this
should be latest (so nearest wins, if equal distance then fallback to
latest).
But this could go in at 2.0.6 IMHO.
-- Kenney
Brett Porter wrote:
Sounds right to me. Needs something mentioned in the
announcement/release notes, though.
- Brett
On 12/02/2007, at 9:25 AM, Jason van Zyl wrote:
Hi,
After looking at MNG-2794 I don't think it's something we should fix
change.
The 2.0.4 release was working in a way contrary to our documentation
in that the nearest with 2.0.4 was not being selected and it is with
2.0.5. So we either fix it and then it conflicts with what we
document, or leave it and have work as documented. That particular
test case also requires commons-collections for compilation and you
should always specify directly any dependencies you need to compile
your project. The details are in the comment, but I say we leave the
behavior that is present in 2.0.5 now.
http://jira.codehaus.org/browse/MNG-2794#action_87295
Thanks,
Jason.
---------------------------------------------------------------------
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]
