The Dependencies are stored in CVS : Preparing Maven Repository Beforehand ???

[Ma...@guardeonic.com]

  Hi all, I barely remember that somebody mentioned this subject but I can 
find the thread anymore.

  The subject is about how do we handle our dependencies, if they are 
stored in the CVS and every build gets a clean version of the whole 
project from CVS. (I use explicitly CVS to avoid the word repository that 
use later to refer to MAven repository).

   Let's say that any project contains a folder called: \lib where all the 
dependencies are stored and refered from project.xml. Any developer is 
asked to keep uptodate the libraries they are using.

   In my case, I have to kick off an external script to move all the 
libraries refered in the project.xml to the corresponding location in the 
Maven repository. This script is kicked off before I can run maven on the 
project. Maven will expect to find all the dependencies in project.xml in 
the maven repository.

  In previous projects, we used Maven central repository to store and 
provide all the dependencies and it was updated by a single person 
(project manager). If you wanted to get the latest version, you only 
needed to clean your local repository and maven retrieved them again from 
the central repository (remote repository). Now, the current project 
mandates to store the dependencies in CVS.


  I wonder whether the way I am currently handling the dependencies is the 
most appropiate way or whether there is other ones.

  Thank you 

   Marcial Rosales


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org