You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Niranjan Rao <nh...@gmail.com> on 2011/07/07 05:29:35 UTC
Setting up internal repository
Hi folks,
I have been researching options for setting up internal maven repository
- free software. Based on my research it seems like nexus is most
recommended choice.
Wondering if people here have any opinions/suggestions.
Ours is a small setup with less than 20 developers. Ideally we would
like to share servers for multiple tasks and would prefer if we can put
behind apache.
We have limited/slow network bandwidth and is one of the important
reasons for setting up the repository. Other reasons such as using same
versions of dependencies etc are of course valid reasons.
Regards,
Niranjan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Setting up internal repository
Posted by Ron Wheeler <rw...@artifact-software.com>.
I am a big fan of Nexus.
It makes Maven actually fun to use.
We used it with a very small team of 4 people.
My only regret is that we did not install it as soon as we started with
Maven. It would have saved a lot of grief.
The free version works very well. We have had absolutely no problems
with our installation.
FOLLOW THE INSTALLATION DIRECTIONS CAREFULLY. It is not a typical
website and if you don't pay attention, you will have to fix it up
before it works.
We have it behind a firewall remote from our development office which
has its own firewall as well.
We also use it from our homes as well with no added fuss.
No problems.
It exposes its own port rather than running through Apache.
We have several repositories defined and aggregated through a repository
group.
The user interface is very nicely structured and it is easy for
developers to use with almost no training.
The documentation is very clear.
Ron
On 06/07/2011 11:29 PM, Niranjan Rao wrote:
> Hi folks,
>
> I have been researching options for setting up internal maven repository
> - free software. Based on my research it seems like nexus is most
> recommended choice.
>
> Wondering if people here have any opinions/suggestions.
>
> Ours is a small setup with less than 20 developers. Ideally we would
> like to share servers for multiple tasks and would prefer if we can put
> behind apache.
>
> We have limited/slow network bandwidth and is one of the important
> reasons for setting up the repository. Other reasons such as using same
> versions of dependencies etc are of course valid reasons.
>
> Regards,
>
> Niranjan
>
>
> ---------------------------------------------------------------------
> 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: Setting up internal repository
Posted by Aldrin Leal <al...@leal.eng.br>.
Here, we often install nexus under a standard tomcat install, and it just
works, sometimes sharing with Jenkins.
Seems not to be a problem, compared to other heavy-weights like the ones
from a major Java Tools supplier I wouldn't dare to name here, which end up
needing to use a full, stand-alone install for each instance.
--
-- Aldrin Leal, <al...@leal.eng.br> / http://www.leal.eng.br/mnemetica/
On Thu, Jul 7, 2011 at 1:15 AM, Niranjan Rao <nh...@gmail.com> wrote:
> Barrie,
>
> Thanks for the quick reply.
>
> When I said "shared server", I meant that we want to have multiple
> applications on the same server - repository application will be one of
> them. I don't know what we will be putting on this server, yet, but one
> thing is for sure, it has to multi task. Based on what you said, it
> seems to be possible.
>
> Other information was very helpful.
>
> thanks for the help,
>
> Niranjan
>
> On Thu, 2011-07-07 at 13:16 +0930, Barrie Treloar wrote:
> > On Thu, Jul 7, 2011 at 12:59 PM, Niranjan Rao <nh...@gmail.com> wrote:
> > > Hi folks,
> > >
> > > I have been researching options for setting up internal maven
> repository
> > > - free software. Based on my research it seems like nexus is most
> > > recommended choice.
> > >
> > > Wondering if people here have any opinions/suggestions.
> >
> > Nexus "Open Source" works (http://nexus.sonatype.org/download-nexus.html
> )
> > Archiva works (http://archiva.apache.org/)
> >
> > Both are open source projects.
> >
> > You'd have to check out the features sets to compare, but I suspect if
> > you picked either you wouldn't have a problem.
> >
> > > Ours is a small setup with less than 20 developers. Ideally we would
> > > like to share servers for multiple tasks and would prefer if we can put
> > > behind apache.
> >
> > These tend to be standalone instances, its not something you need to
> > put behind apache.
> >
> > Why do you want to "share servers"?
> > One repository manager instance is plenty.
> > Once the repo manager has downloaded the artifact it doesn't do much
> > but serve it out again, once each developer has a local copy the repo
> > manager doesn't do anything but idle.
> >
> > > We have limited/slow network bandwidth and is one of the important
> > > reasons for setting up the repository.
> >
> > This is a good reason, speed of downloading is better since its all
> > local network traffic.
> >
> > > Other reasons such as using same
> > > versions of dependencies etc are of course valid reasons.
> >
> > You dont get this from a repo manager.
> > You get this from maven and locking down versions in your poms and
> > using enforcer and enable the convergence rule
> >
> http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html
> >
> > If you want to have a repo manager that contains only "sanctioned"
> > artifacts I think you are need to buy Nexus Pro.
> > I dont know if Archiva has this feature.
> > Or you need to manually work this process somehow.
> >
> > ---------------------------------------------------------------------
> > 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: Setting up internal repository
Posted by Niranjan Rao <nh...@gmail.com>.
Barrie,
Thanks for the quick reply.
When I said "shared server", I meant that we want to have multiple
applications on the same server - repository application will be one of
them. I don't know what we will be putting on this server, yet, but one
thing is for sure, it has to multi task. Based on what you said, it
seems to be possible.
Other information was very helpful.
thanks for the help,
Niranjan
On Thu, 2011-07-07 at 13:16 +0930, Barrie Treloar wrote:
> On Thu, Jul 7, 2011 at 12:59 PM, Niranjan Rao <nh...@gmail.com> wrote:
> > Hi folks,
> >
> > I have been researching options for setting up internal maven repository
> > - free software. Based on my research it seems like nexus is most
> > recommended choice.
> >
> > Wondering if people here have any opinions/suggestions.
>
> Nexus "Open Source" works (http://nexus.sonatype.org/download-nexus.html)
> Archiva works (http://archiva.apache.org/)
>
> Both are open source projects.
>
> You'd have to check out the features sets to compare, but I suspect if
> you picked either you wouldn't have a problem.
>
> > Ours is a small setup with less than 20 developers. Ideally we would
> > like to share servers for multiple tasks and would prefer if we can put
> > behind apache.
>
> These tend to be standalone instances, its not something you need to
> put behind apache.
>
> Why do you want to "share servers"?
> One repository manager instance is plenty.
> Once the repo manager has downloaded the artifact it doesn't do much
> but serve it out again, once each developer has a local copy the repo
> manager doesn't do anything but idle.
>
> > We have limited/slow network bandwidth and is one of the important
> > reasons for setting up the repository.
>
> This is a good reason, speed of downloading is better since its all
> local network traffic.
>
> > Other reasons such as using same
> > versions of dependencies etc are of course valid reasons.
>
> You dont get this from a repo manager.
> You get this from maven and locking down versions in your poms and
> using enforcer and enable the convergence rule
> http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html
>
> If you want to have a repo manager that contains only "sanctioned"
> artifacts I think you are need to buy Nexus Pro.
> I dont know if Archiva has this feature.
> Or you need to manually work this process somehow.
>
> ---------------------------------------------------------------------
> 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: Setting up internal repository
Posted by Barrie Treloar <ba...@gmail.com>.
On Thu, Jul 7, 2011 at 12:59 PM, Niranjan Rao <nh...@gmail.com> wrote:
> Hi folks,
>
> I have been researching options for setting up internal maven repository
> - free software. Based on my research it seems like nexus is most
> recommended choice.
>
> Wondering if people here have any opinions/suggestions.
Nexus "Open Source" works (http://nexus.sonatype.org/download-nexus.html)
Archiva works (http://archiva.apache.org/)
Both are open source projects.
You'd have to check out the features sets to compare, but I suspect if
you picked either you wouldn't have a problem.
> Ours is a small setup with less than 20 developers. Ideally we would
> like to share servers for multiple tasks and would prefer if we can put
> behind apache.
These tend to be standalone instances, its not something you need to
put behind apache.
Why do you want to "share servers"?
One repository manager instance is plenty.
Once the repo manager has downloaded the artifact it doesn't do much
but serve it out again, once each developer has a local copy the repo
manager doesn't do anything but idle.
> We have limited/slow network bandwidth and is one of the important
> reasons for setting up the repository.
This is a good reason, speed of downloading is better since its all
local network traffic.
> Other reasons such as using same
> versions of dependencies etc are of course valid reasons.
You dont get this from a repo manager.
You get this from maven and locking down versions in your poms and
using enforcer and enable the convergence rule
http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html
If you want to have a repo manager that contains only "sanctioned"
artifacts I think you are need to buy Nexus Pro.
I dont know if Archiva has this feature.
Or you need to manually work this process somehow.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org