Hi,
do you really need HTTP PUT for your repo? Can you not do scp or even
file? Also, maybe you want to use maven-proxy, which is old, but very
lightweight, stable and and can serve from a custom repository plus acts
as a cache for repo1 (central), which saves you bandwidth and time.
Also, it is very easy to configure.
Stefan
Todor Boev wrote:
Hello,
I'm a maven uber-newby. Been playing with it since 2 days ago :)
Currently I need to set up an HTTP visible maven repo on a resource
constrained box. It has some linux - don't know the distro, and an old
Apache 1.3 web server. I tried to simply designate a directory to be the
repo and made it accessible via the apache (enabled indexing for the
dir). As expected maven could download from that directory but could not
put jars back into into it (HTTP PUT doesn't work). I need to know if it
is possible to just tweak apaches config a bit more to make the repo
fully functional. I hope I don't need to deploy something like Nexus -
it doesn't leave enough resources for the elaborate Ant-based build
system that also lives on the linux box (pentium III, 512 mb ram, 8gb
hdd)
Cheers,
Todor
---------------------------------------------------------------------
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]
