Re: [picocontainer-dev] build improvements

Konstantin Priblouda <kpriblouda-/[email protected]>
Newsgroups gmane.comp.java.picocontainer.devel
Message-ID <[email protected]>
--- 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. 

regards,




----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/


      ____________________________________________________________________________________Shape Yahoo! in your own image.  Join our Network Research Panel today!   http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 



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

    http://xircles.codehaus.org/manage_email
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.