On 12-Apr-08, at 9:24 AM, Peter Horlock wrote:
Which Repo Manager would you prefer?
I'm openly and wholly biased because my company produces Nexus. So I'm
not the one to ask for a non-partisan opinion.
Sonatype Nexus or Maven Archiva? Nexus is well documentated in the
Sonatype
Maven book, which is a big plus imho,
and I also read it's supported by their Eclipse Maven (m2eclipse)
plugin,
which is probably also quite helpful.
Facts that are certain:
- Tamas has worked the longest on any repository manager, first with
proximity and now with Nexus. He works on Nexus full-time a fact of
which I'm very proud of.
- Nexus has the most thorough documentation with the chapter in the
maven book and this will be expanded as we add more features.
- Nexus integrates best with Eclipse in the form of m2eclipse and
that's certainly due to the fact that we (Sonatype) work on both. That
integration will become richer very rapidly. Nexus is already also
used in the Netbeans integration, and will be in IDEA as well. So the
most popular form of IDE integration already is, or will be using
Nexus technologies. We already have index proxying working as well
which is very cool. So when you proxy Maven central for example, you
can search Maven central's index without requiring a full mirror
- We have no external resource dependencies like databases which is a
huge plus in large environments. We know this for a fact because aside
from Google we are working with and talking to companies which have
very large IT infrastructures and developer populations and
introducing a database requirement just makes your adoption/
procurement process a lot harder.
- Nexus already has a complete REST API which will be the cornerstone
of 3rd party integration. We use Restlet and are working with the
Restlet authors to provide optimal and secure REST access.
- We are fixing errors in Nexus very quickly. The beta-2 was released
very shortly after the beta-1, and this will continue toward the 1.0.
- We don't require WebDAV for deployment, we actually figured out a
way to use REST with a simple PUT for deployment which greatly
simplifies the client side not requiring WebDAV. All one should care
about is security, and DAV doesn't really help here and REST just
makes things far simpler.
However, Archiva seems to be the most stable Repo Manager.
More stable in what way?
I suggest as an exercise for yourself use the Apache Benchmark tool
(comes standard with apache) and hammer both Archiva and Nexus and
decide for yourself which one is more stable.
Load up Nexus' default distribution and Archiva's default distribution
with a profiler and judge for yourself what the foot prints are for
use. We will create some benchmarks for people to look at but we are
very sensitive to resource use and performance. We're working with the
Jetty authors to utilize the Jetty client library and creating a
memory file map cache to serve out heavily used artifacts at near
static content speeds.
It's really hard to decide.
I would be interested in everyone else's opinions.
http://weblogs.java.net/blog/johnsmart/archive/2008/04/nexus_my_next_m.html
Ultimately you have to try them both and decide. Try setting them both
up and see what you think. Compare the integration with Eclipse with
your developers and let them help you decide. Also join the mailing
lists and measure how fast releases come out, and how quickly issues
are dealt with as this is an important aspect as well.
Thanks,
Peter
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
