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 different. "My" original code does not require commons-collections for compilation, but it relies on 2 components which require 2 different versions of this library. So commons-collections is actually required, but for runtime only (the build broke during the execution of the unit tests). As Brett said, this should be mentioned clearly in the release notes because lots of people may be surprised.
Fabrice. On 2/11/07, Jason van Zyl <[EMAIL PROTECTED]> 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]
