Most people on this list set up a corporate-wide Maven Proxy of some kind to resolve this situation. Search the list for "proxy" and you'll find a lot of information about it.
Wayne On 11/6/06, Manish Shah <[EMAIL PROTECTED]> wrote:
Hi there, We have a m2 build with three modules (A,B and C) configured. The dependencies are as follows: A -> B, B -> C. We have a company m2 repository set up on our network. The repository is used for 3rd party dependencies, not our own modules. However, when we build on a developers machine, maven attempts to serach the company m2 repository to look for modules A, B and C. Is there any way to disable this behaviour? These modules will never be published to the repository and so we'd like the maven build not to attempt to find them there. This behaviour causes us an issue because a developer cannot build unless he is not connected to the network. Thanks, Manish This email is intended only for the use of the addressees named above and may be confidential or legally privileged. If you are not an addressee you must not read it and must not use any information contained in it, nor copy it, nor inform any person other than TietoEnator or the addressees of its existence or contents. If you have received this email and are not a named addressee, please delete it and notify the TietoEnator UK Technical Services Team on 0113 390 0700.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
