What you are referring to as a "external" repository is essentially a caching proxy.
If the only repository you are proxying is central, then theoretically you could use any caching proxy server (including Apache). But if you are a single developer, I'm not sure what value you are looking to get out of this. Your local Maven repository acts as a local cache, so unless you need to blow this away with some regularity, what's the point? Justin On 8/16/10 4:16 AM, Trevor Harmon wrote: > Hi, > > I've set up an "internal" repository for deploying project artifacts. It was > remarkably easy to do. All I needed was some web space with SCP access. After > that it was only a matter of configuring my POM's <distributionManagement> to > point to the URL. No repository manager needed. > > Now I'd like to set up an "external" repository. (Not sure if that's the > right term.) The only purpose would be to cache artifacts so that Maven can > download them from my repository instead of making a trip out to Central. > > However, it appears that this type of repository is not so easy to set up. My > understanding is that it would require the use of a repository manager. I'm > hoping to avoid that, since repository managers have to run as a background > service (e.g., in a Java EE container). This would really complicate things, > mainly because I don't have root access to the server and would have to get > special permission to set up the service. > > Am I correct in thinking that an external repository necessarily requires > setting up a repository manager? Thanks, > > Trevor > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
