Hi,
I have experiece with exact this setup. It is not very good or one reason:
Network traffic and latency. If you use a network share, everyone
accessing the local repo has a classpath consosting of network mapped
jars. If you use eclipse for example, this has a serious performance
impact!
There is another major drawback, although on first sight it sounds like an
advantage: every developer gets every change installed to the local repo.
This means, is it not possible to install small in develop changes to the
repo and experiment with them, because any other developer in your company
gets this change, too.
I can only discourage this kind of use of maven (1&2).
Greetings,
Christian Domsch.
On Wed, 21 Jun 2006 08:41:31 +0200, Aleksei Valikov <[EMAIL PROTECTED]>
wrote:
Hi.
I'm introducing Maven in my company. We're not a very large firm, ~ 20
developers and I consider if we should use a common local repository -
for instance over a network share.
The problem is that we often use non-released versions of third party
libraries, which do not exist in central repositories like ibiblio.
Another thing that our projects sometimes depend on non-released
artifacts (like jta or jsf-facelets). If we use a common local
repository, it would be enough that just one developer installs these
artifacts into a local repo - and they immediately become available to
everyone.
Do you do anything similar? Are there drawbacks? What is the recommended
approach?
Bye.
/lexi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
