This is the best solution. Another advantage is that if you find a bug in a dependency pom, you can submit an issue to Maven team and fix it in your internal repo until it is fixed in the main repo.
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]
