You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Todor Boev <t....@prosyst.bg> on 2008/08/27 09:36:36 UTC
Simplest possible http repo setup?
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Simplest possible http repo setup?
Posted by Chad La Joie <ch...@switch.ch>.
Hey Todor,
You can simply use SSH (SCP) to move your artifacts up to the
repository. Your Linux box is probably already running sshd.
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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
SWITCH
Serving Swiss Universities
--------------------------
Chad La Joie, Software Engineer, Net Services
Werdstrasse 2, P.O. Box, 8021 Zürich, Switzerland
phone +41 44 268 15 75, fax +41 44 268 15 68
chad.lajoie@switch.ch, http://www.switch.ch
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Simplest possible http repo setup?
Posted by Jason van Zyl <ja...@sonatype.com>.
On 27-Aug-08, at 1:01 AM, Haikal Saadh wrote:
> You'll have to look into mod_dav or similar for apache. That'll give
> you http put.
>
> Or, you can run something like Archiva in standalone mode, using the
> embedded jetty. (That'll give you an mirror of other repos as well,
> among with some other nice features)
Nexus is way less resource intensive then Archiva. Nexus just uses
embedded Jetty and allows a simple PUT to deploy. Nexus runs at a
constant 28mb of memory, it's pretty light relatively speaking.
>
>
>
>
> On 27/08/2008, at 5:36 PM, 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
believe nothing, no matter where you read it,
or who has said it,
not even if i have said it,
unless it agrees with your own reason
and your own common sense.
-- Buddha
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Simplest possible http repo setup?
Posted by Haikal Saadh <sp...@gmail.com>.
You'll have to look into mod_dav or similar for apache. That'll give
you http put.
Or, you can run something like Archiva in standalone mode, using the
embedded jetty. (That'll give you an mirror of other repos as well,
among with some other nice features)
On 27/08/2008, at 5:36 PM, 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Simplest possible http repo setup?
Posted by Todor Boev <t....@prosyst.bg>.
Stefan Seidel wrote:
> 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
>
>
Actually scp is an equally good alternative to http put. Don't really
know why I assumed HTTP to be the simplest way to publish the repo for
remote access. Thanks for the suggestion.
Btw I did try web-dav today but somehow it does not work :P
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Simplest possible http repo setup?
Posted by Stefan Seidel <ss...@vub.de>.
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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Simplest possible http repo setup?
Posted by Geoffrey Wiseman <ge...@gmail.com>.
On Wed, Aug 27, 2008 at 3:36 AM, Todor Boev <t....@prosyst.bg> wrote:
> 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)
Nexus is pretty light, i'm given to understand -- but I respect the fact
that that's a pretty resource-constrained box as well. When your build
system is outpowered by current cell-phones, perhaps it's time to upgrade
the build system?
- Geoffrey
--
Geoffrey Wiseman