Hi Scott, On 02/03/07, Scott Ryan <[EMAIL PROTECTED]> wrote:
Why was the "nearness" process chosen and what does it buy me over using the most current compatible version out of my entire dependency list?
Yep, nearness has never made much sense to me either. The proper fix for the more natural highest-wins strategy is covered in http://jira.codehaus.org/browse/MNG-612. I hope to allocate some time to implement this in the not-to-distant future.
How can I insure that I don't get my dependencies randomly downgraded so that I get runtime errors with no indication until I use the application?
Dependency management would help you here, although it's broke for transitive dependencies ;) See http://jira.codehaus.org/browse/MNG-1577.
Is there a report or process I can use to locate these downgrades so I can deal with them during build time and not runtime?
Unfortunately, only mvn -X compile currently shows these conflicts. I've got plans to incorporate this very useful conflict information into the help:dependencies dependency tree via an optional flag. Alternatively, a separate dependency:conflicts goal could make more sense, but nothing is implemented as yet. Cheers, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
