baerrach wrote: > >> So are there workarounds? >
Sorry if I'm coming late into this and missed some of the finer points but we are currently using maven proxy (with an eye to Archiva or Proximity when they are finally manage a production quality release) to provide us with some control over the repo access order and to prevent our maven projects from having to be littered with lots of differing pom.xml defined repo declarations. Using the proxy as intermediary has the added benefit of allowing us to obscure artifacts present in one repository with those in others. Maven itself is only every talking to 2 repos, our RELEASE proxy and our SNAPSHOT proxy. the RELEASE proxy repo order looks something like this: inhouse.corporate.release inhouse.central-ovveride.release external.central.release external.codehaus.release ... Where inhouse.central-override.release does what it says on the tin, namely verrides artifacts defined in central with our own custom built versions. Would this not work for most corporate instances? -- View this message in context: http://www.nabble.com/Patched-artifacts-resolved-incorrectly-from-internal-repository-tf2811385s177.html#a7889657 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
