This is a really bad idea/suggestion. If you're actually doing this in production, I feel bad for you!!
The local repository is (currently) assumed by Maven to be a single user, single threaded access kind of environment. So it is also a bad idea to have multiple Maven builds executing at the same time. Some plans have been discussed on dev@ to make it more capable/resilient, but nothing has thus far been implemented, so this is the current state of things. Multiplying the effects of multiple threads accessing the same local repo like this across many (10s or 100s) developers would break things in really ugly ways. Do NOT do this! Wayne On Dec 25, 2007 9:10 AM, Ari Jeremy <[EMAIL PROTECTED]> wrote: > Well, if what Smoak has pointed looks weird/heavy to you then can think of > following simplest solution... > > Assuming yours is windows environment.. > > 1 Have a central machine that will host all the required artifacts fro your > project. Run all possible goals on this machine so that maven download > required artifacts from internet nd store in ~/.m2/repository. > > 2 Share "C:\Documents and Settings\user\.m2" folder on this machine > > 3 Ask your developers to add following (note: ip needs to be changed) under > <settings> element in maven-installation-folder/conf/settings.xml file. > > *<localRepository>\\9.12.14.15\.m2\repository</localRepository>* > > What we are doing effectively here is: Settingup a repository locally on a > central machine and using it for all the intranet users as local repository. > > Hope that will solve the issue for you... > > Thanks, > Ari Jeremy > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
