I agree with Matt. I would like to keep my project specific lib dir seperated from the 
central maven one. If I
use  maven.repo.remote the jars would still be copied to the central repo. I would 
like to have the option of
keeping them seperate.

Age


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 11, 2002 04:22
> To: Turbine Maven Developers List
> Cc: [EMAIL PROTECTED]
> Subject: Re: proposal for another lib directory
>
>
>
> This really belongs on turbine-maven-user, so I'm copying there.
>
> maven.repo.remote is a comma separated list of urls. These can be file://
> urls. This allows you to do what you want, right?
>
> The 'centralised' repository could theoretically be on a per project basis
> if you like.
> --
> dIon Gillard, Multitask Consulting
> Work:      http://www.multitask.com.au
> Developers: http://adslgateway.multitask.com.au/developers
>
>
>
>
>                     "Matt Ho"
>
>                     <matt@indigoeg       To:     "'Turbine Maven Developers List'"
>
>                     g.com>                <[EMAIL PROTECTED]>
>
>                                          cc:
>
>                     06/11/02 12:21       Subject:     proposal for another lib 
>directory
>
>                     PM
>
>                     Please respond
>
>                     to "Turbine
>
>                     Maven
>
>                     Developers
>
>                     List"
>
>
>
>
>
>
>
>
>
> Maven is currently design to allow any number of projects to share a
> common repository of JAR files.  However, as a consultant I believe that
> trying to get our clients to set up a centralized repository doesn't
> make a lot of sense.
>
> I propose that we allow maven to look in multiple directories for its
> libraries.  The intent would be to allow jar files to be shipped with
> the source code.  It might work by adding another property such as
> project.repo or maven.repo.project to a local directory (probably within
> the project) where the jar files could be found.
>
> Alternatively, we could modify maven.repo.remote so that it takes
> relative paths on the local file system or even create a
> maven.repo.local.
>
> I would favor creating a maven.repo.project that maven doesn't copy to
> the shared repository (lib.repo).  Any thoughts?
>
> M
>
>
>
> --
> To unsubscribe, e-mail:   <
> mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <
> mailto:[EMAIL PROTECTED]>
>
>
>
>
>
>
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>


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

Reply via email to