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
Hope it will be in the next 2.0.6
Cheers,
Vincent
2007/2/12, Trygve Laugstøl [EMAIL PROTECTED]:
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
Hi Jason,
the aim of this particular test case I implemented was to reproduce the bug.
I made it simple to show the issue, and I agree that if you use a class for
compilation, you should specify it as a dependency in your POM. However, the
problem I had when I found this issue was slightly
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
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
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
+1
Yep, i guess this is going to become a FAQ on the list and on IRC :-)
Rahul
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
Hi Jason,
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
