RE: [picocontainer-dev] build improvements

Konstantin Priblouda wrote on Tuesday, May 22, 2007 10:55 AM:

> --- Mauro Talevi <[email protected]> wrote:
> 
>> I would leave cobertura as it does a good enough job
>> and needs no license.
> 
> OK, then good bye clover.
> 
>>> what value  has specifying test dependencies in
>>> <dependencyManagement/>  and then in <dependencies/>
>>> on parent?
>> 
>> dependencyManagement takes care of versions and
>> (possible) exclusions.
>> 
>> dependencies declares the dependency for all
>> children (without versions or exclusions).  So it
>> makes
>> sense to have both if a dependency - eg junit - is
>> used by all children.
>> 
>> dependencies declared in management can also be used
>> by children, of course.
> 
> groked documentation  - not that simple ;)
> 
> dependencies are inherited by all children down the
> tree,  dependencyManagement olny if they like, and
> there is possibility to override stuff.
> 
> Exclusion / inclusion / scoping works the same way.
> 
> DM is good for dependencies on container  / gems / tck
> ( to avoid version specification everywhere )
> 
> tck also uses it to override scope for junit etc.

Basically dep versions should onlyx be declared in the depMgnt, never in the dep directly. Not all POMs might be up-to-date.

- Jörg

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email