Hi Dion, I haven't use this feature "jar overrides" so I don't how it 
works. 

Does "jar override" means that you specify in the dependency's field "jar" 
your location instead of the default one made up by Maven? 






[EMAIL PROTECTED] 
11/12/2003 14:00
Please respond to
"Maven Users List" <[EMAIL PROTECTED]>


To
"Maven Users List" <[EMAIL PROTECTED]>
cc

Subject
Re:   Réf. : The Dependencies are stored in CVS : Preparing Maven 
Repository Beforehand ???






Why not use jar overrides, and point the jar override at ./lib?
--
dIon Gillard, Multitask Consulting
Blog:      http://blogs.codehaus.org/people/dion/



[EMAIL PROTECTED] wrote on 12/12/2003 12:41:58 AM:

> Hi Nicolas, as I said in the mail, in previous projects that was the way

> we worked. But now, this project mandates that the libraries should be
in
> cvs. I can't get away from that.
>
>  I definitely like the way Maven suggests to handle the dependencies.
>
>  Thank you, Nicolas.
>
>
>
>
>
> [EMAIL PROTECTED]
> 11/12/2003 12:42
> Please respond to
> "Maven Users List" <[EMAIL PROTECTED]>
>
>
> To
> "Maven Users List" <[EMAIL PROTECTED]>
> cc
>
> Subject
> Réf. : The Dependencies are stored in CVS : Preparing Maven Repository
> Beforehand ???
>
>
>
>
>
>
> Why don't use SNAPSHOT version for your dependency and on a local server
> store the jar who can't be in ibiblio. It seem to be the way method to
> have latest version than storing them in CVS. With maven i think that
lib
> don't have to be in CVS because it have a mechanism to find them
> automaticly.
>
> Nicolas
>
>
>
>
>
> [EMAIL PROTECTED]
> 11/12/2003 12:33
> Veuillez répondre à "Maven Users List"
>
>
> Pour :  Maven Users List <[EMAIL PROTECTED]>
> cc :
> Objet : The Dependencies are stored in CVS : Preparing Maven Repository
> Beforehand
> ???
>
>
> 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to