I think I may need a concrete example to make sure I understand the
issue properly. However, in my opinion dependency management
specifications should be used for anything not explicitly specified.
For example,
parent
foo
1.0.0
runtime
parent
ch
On Fri, Jan 9, 2009 at 10:35 AM, Oleg Gusakov
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
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 depen
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
spec
