Your life would be much easier using a repository manager for your "internal" repository. Nexus is almost trivial to set up, for example.
As for internal vs external, there is no difference, you don't need a repository manager... but your life will always be easier if you use one. -Stephen P.S. I only mention Nexus because it is the repository manager I have had good experience with. On 16 August 2010 09:16, Trevor Harmon <tre...@vocaro.com> 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: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
