Hi all, I'm working on wrapping my head around setting up an internal "blessed" repository and being assured that Maven will fail when a dependency is not found there.
(1) Clear my local repo. (2) Run Maven through our lifecycle (clean, compile, package, test, etc.). (3) Take the contents of my now-populated local repo and copy them up to a shared location. Now I'm not sure what to do next. I've tried overriding both the central repo and plugin repo with my local repo in our POMs, however this consistently seems to ignore plugins that are found in my internal repo (i.e. claim they aren't there when they are). It also attempts to check for updates to plugins that aren't -SNAPSHOT versions and I'm not sure quite why. Given the trouble I'm having, I'm pretty sure I'm way off the reservation here with what and how I'm doing this. Looking inside the repo, there are central XML files that Maven is probably surprised to find inside the local repo? I'm not terribly interested in adding another piece of software to our build environment, hence my avoidance of a Repository Manager. We have a very small number of dependencies outside of our project. Maven's own dependencies dwarf ours :) Any tips are much appreciated, thanks! Rob
