Everyone has different needs, so you should consider what you're
looking for. I hesitate to jump into direct comparisons for that reason.
However, from a functional perspective, there is the repository
manager matrix that might help:
http://docs.codehaus.org/display/MAVENUSER/Maven+Repository+Manager+Feature+Matrix
From what I can tell, as of 1.1 Nexus has basically caught up on most
features it didn't have that Archiva did.
I believe Archiva still uniquely has:
- more extensive WebDAV support (if you need to use a WebDAV client
like those built into the operating system)
- more artifact information in the UI
- built in user management rules such as password expiry, account
locking, etc.
Of course, some use cases are addressed differently in each
application and you may prefer one or the other.
From a non functional perspective, there are some differences:
- Apache License
- independent, hosted at Apache
- developed by a diverse group of contributors
Whether those are advantages or not really depends on how you intend
to use the source code or whether you want to be directly involved in
development.
I'm still glad you're currently using Archiva and hope it continues to
satisfy you :)
Cheers,
Brett
On 04/12/2008, at 3:03 AM, solo1970 wrote:
can anyone give me the advantages of using Archiva vs Nexus????
Sonia
P.S. We are currently using Archiva
--
View this message in context:
http://www.nabble.com/Archiva-vs-Nexus--tp20815821p20815821.html
Sent from the archiva-users mailing list archive at Nabble.com.
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
