About http://jira.codehaus.org/browse/MNG-2794
Maven 2.0.4 uses the "nearest" strategy to solve dependency conflicts, so the issue " project depends on A -> D-v2 project depends on B -> D-v3 " has no determinist solution about what version of D will be transitively used. Is there some change in resolution strategy with 2.0.5 ( http://docs.codehaus.org/display/MAVENUSER/Improving+Maven2+Dependency+Resolution) or does this target maven 2.1 ? Nico. 2007/2/8, franz see <[EMAIL PROTECTED]>:
Good day, There are two issues left for 2.0.5. Feel free to speed things up :) Cheers, Franz [1] http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10500&fixfor=12294 Adam Lewis-7 wrote: > > My guess is around the one year anniversary of 2.0.4. > > > > On 2/6/07, Thierry Lach <[EMAIL PROTECTED]> wrote: >> >> Any idea when Maven 2.0.5 will be released? >> > > -- View this message in context: http://www.nabble.com/Maven-2.0.5-release-plans--tf3181525s177.html#a8869622 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
