Hello, > The releases of your companies artifacts can't use snapshot versions > and internally patched versions of the plugins needs to be made > available to all developers.
I solved these issues by writing my own proxy which can rewrite URLs (so even if someone configures Maven to download something from Xyz.com, it will still go to Sateh, no matter what). Plus I can "blind" maven (return 404 for any URL I like). This way, I can make a beta of the site plugin (which contains vital bug fixes for me) available to all developers but maven will not be able to download the snapshots of the source or compiler plugin. As a last resort, the proxy will look into a "patches" tree for files. The search order is: patches, allow/deny rules, rewrite rules. This allows me to fix any bugs by using my own patches, let maven see what it should (and nothing else) and force all external connections to one single maven repository. Regards, -- Aaron Digulla --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
