Thank you for the link. I had looked at this section from teh book around a year back. I couldnt find any clear advantage since we have a pre approved and pre decided list of plugins and dependencies.
Currently we have a master repository which is populated only when project decides to add a new dependency or plugin. At teh initial hudson setup, this repository is copied to a private location, and hudson is pointed to this private location ( this is one time only and is not done with each build ). Build is done in the offline maven mode. Given this scenario, Im trying to see if repository managers can provide any advantage over what we already have. --sony 2011/4/20 Tamás Cservenák <[email protected]> > See here for reasons: > > > http://www.sonatype.com/books/nexus-book/reference/sect-repoman-reasons.html > > > Thanks, > ~t~ > > On Wed, Apr 20, 2011 at 2:23 PM, Sony Antony <[email protected]> > wrote: > > > Im trying to evaluate whether we should use a repository manager. > > > > Will somebody post at least a few of the advantages here > > Our project uses a list of pre approved ( and pre downloaded ) > dependencies > > and plugins. > > > > --sony > > >
