On 11/23/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Any answers to this (may be too long :) ) question ?
It was fairly long and involved. :) A few thoughts... I'm leaning towards settings.xml with the appropriate Proximity repository defined as a mirror of central. You can create a "custom" versions of maven by modifying the settings.xml in the maven distribution. That way you're sure that everyone is using the appropriate settings. Or you can provide instructions for developers to modify their local settings.xml files. If your integration testers are using the second Proximity repository as a mirror of central, (and no other repositories,) the build will fail if the artifacts aren't present. My concern (without trying it) is that a lot of poms add additional <repositories>, and I'm not sure how you're going to prevent those from being used. (Other than isolating the build machine so it doesn't have access to anything but the repository you've set up.) -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
