BTW be careful about the words you use : internal repository is not
the same as a local repository. A local repository should be only
local to a developer desktop and not on a network drives or you will
have speed issues.

On 6/21/06, 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]



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

Reply via email to