On Fri, Jan 9, 2009 at 10:35 AM, Oleg Gusakov <oleg.subscripti...@gmail.com>wrote:
> > Shane Isbell wrote: > >> I've run into an issue where the current behavior of building a project >> model in Maven 2.0.x seems wrong. In the case of inheritance of dependency >> scope, there is a default value of "compile". This default will override >> the >> parent scope. This part is correct. But if the dependency scope is not >> specified, the default value CAN be overridden by the dependency >> management >> section of the pom. So in one case, the default value can't be overridden, >> but in the other case it can. >> >> >> > In Mercury ommitted scope is always set to compile, regardless on > inheritance. But POM is proceessed by Maven, and whatever mechanism is used > there - Mercury gets back. That raises an interesting point because if you specify scope as 'compile' explicitly, as you do in Mercury, dependencyManagement will apply differently than having scope 'compile' implicitly given. It's even more important to get this defined correctly with Mercury in the mix. Shane
