maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wendy Smoak" <>
Subject Re: Environment management - I am not sure what to call it really!
Date Fri, 22 Feb 2008 19:07:10 GMT
On Fri, Feb 22, 2008 at 11:51 AM, Arash Bizhan zadeh <> wrote:

> If I put dependencies there, wouldn't all projects download them even though
>  they may not really need them? Can Archiva help us in this situation?

Wayne said <dependencyManagement>, not <dependencies>.  The former is
more like a suggestion to the child project-- if the child project
declares a dependency and leaves out the version, it will get the
version from the parent's <dependencyManagement> section.

A child project can still override this, so you can't force the
version number from the parent.

Yes, Archiva can help.  You can control the contents so that
developers don't have access to things that are not approved.

(You'll need to use mirrors, and especially mirrorOf * in settings.xml
to prevent access to external repositories.)


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message