Maybe I wasn't thinking about this problem the right way.
It turns out that when I override the Super POM's "central" repository entry using my project's POM, with <enabled>false</enabled> for both <snapshots> and <releases>, maven2 exhibits the desired behavior. The build now (correctly) fails for artifacts that would have been obtainable from central, which are not found in my blessed repository. Maven continues to download the plugin artifacts it requires from central. Problem appears to be solved. If any of you know of issues that are likely to arise using this approach, please reply. Thanks, -- Tommy On 1/12/07, Thomas Knowlton <[EMAIL PROTECTED]> wrote:
I am in the process of migrating the build of a largish project from Ant to Maven 2. I'm trying to figure out whether it's possible and how to configure a Maven project to depend on artifacts from a given repository ONLY. That is, I want to restrict Maven's search path to a "blessed" repository, for artifacts that my project directly depends on; however, I don't want to prevent Maven being able to get its plugins (and their dependencies) from our (internal) mirror of central (containing "unblessed" artifacts). I was wondering about the difference between <repositories> and <pluginRepositories>, but I haven't figured out from the documentation how to use them to accomplish this. Does anybody know, is it possible to do what I'm describing? If so, could you post a snippet? Thanks for your time. -- Tommy
-- -- Tommy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
