Well for starters the index is generated in real time for internal repos and it can be downloaded/proxied from the remote repos, both in a way that m2e understands out of the box. Based on this thread it seems that even using the nexus-indexer cli, archiva won't serve the index.
The configuration of Nexus is faster and more flexible both in concept and in responsiveness of the UI. The memory and possibly processor footprint is much smaller than Archiva and it should scale better. I have started doing some profiling of all the repo managers and will publish my results soon. Granted, right now Nexus isn't supporting all the same features as the others but they are on the roadmap I'm about to publish and will be there very soon. I think the performance footprint and the UI is where we stand out currently and for architectural reasons I don't believe the others will be able to keep up. Again, the results will be published when I finish the profiling. -----Original Message----- From: manuel aldana [mailto:[EMAIL PROTECTED] Sent: Friday, April 18, 2008 6:03 PM To: [email protected] Subject: Re: [m2eclipse-user] Problem with binding maven indexes (Nexus) > Yes and yes. You can download it from http://nexus.sonatype.org/ > And see part of the admin UI in action at > http://repository.sonatype.org/ looks really nice! never the less as we currently are using archiva and it serves us well i don't see a reason why to switch, or is there a one unique selling point for nexus? -- manuel aldana [EMAIL PROTECTED] homepage: http://www.aldana-online.de --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
