You should discuss this in the Nexus forum.
Nexus is easy to st up and does not require a separate container.
It does both internal and external with proper access control.
Other repository solutions may also work but I use Nexus for my
development team.
Ron
On 16/08/2010 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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
