Comments on: The Hype About Repository Managers http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/ Thoughts to ponder.. Thu, 09 Sep 2010 04:52:49 +0000 http://wordpress.org/?v=2.3.1 By: Deng Ching http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-394 Deng Ching Sun, 31 Aug 2008 07:24:37 +0000 http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-394 Ok, thanks Brian! Ok, thanks Brian!

]]> By: Brian Fox http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-390 Brian Fox Fri, 29 Aug 2008 13:21:18 +0000 http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-390 I updated the matrix with new information and put it on the wiki so we can all keep it updated: http://docs.codehaus.org/display/MAVENUSER/Maven+Repository+Manager+Feature+Matrix I updated the matrix with new information and put it on the wiki so we can all keep it updated:
http://docs.codehaus.org/display/MAVENUSER/Maven+Repository+Manager+Feature+Matrix

]]> By: Deng Ching http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-101 Deng Ching Tue, 06 May 2008 11:39:07 +0000 http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-101 dmitry, I think only Artifactory currently has this GUI feature for deployment. This would be a new feature in Archiva 1.1 though. It's actually available in svn trunk now, it just hasn't been released yet :-) dmitry, I think only Artifactory currently has this GUI feature for deployment.
This would be a new feature in Archiva 1.1 though. It’s actually available in svn trunk now, it just hasn’t been released yet :-)

]]> By: Deng Ching http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-100 Deng Ching Tue, 06 May 2008 11:36:52 +0000 http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-100 Thanks Kostis for posting the new features of Artifactory :) Thanks Kostis for posting the new features of Artifactory :)

]]> By: dmitry http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-59 dmitry Thu, 03 Apr 2008 23:40:29 +0000 http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-59 are any of the repo managers offer a GUI alternative to "mvn deploy:deploy-file"? are any of the repo managers offer a GUI alternative to “mvn deploy:deploy-file”?

]]> By: Kostis http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-49 Kostis Thu, 20 Mar 2008 15:07:01 +0000 http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-49 Concerning Artifactory, version 1.2.5 has many new features not available in 1.2.2 (the one mentioned here): * Proxies also Maven1 repositories. * Virtual Repositories - Aggregate content view of any number of local and remote repositories combined. * Automatic cleanup of unique snapshots. * WebDAV support for browsing, listing, deploying and undeploying (apart from UI). * Full system import/export (ala JIRA/Confluence) including security settings. * Scheduled repository backups. * Import/Export and backup to standard Maven 2 file-based repositories. * Configuration can be dynamically reloaded in runtime from the UI. No need to restart. Thank you for your effort compiling those facts. Concerning Artifactory, version 1.2.5 has many new features not available in 1.2.2 (the one mentioned here):
* Proxies also Maven1 repositories.
* Virtual Repositories - Aggregate content view of any number of local and remote repositories combined.
* Automatic cleanup of unique snapshots.
* WebDAV support for browsing, listing, deploying and undeploying (apart from UI).
* Full system import/export (ala JIRA/Confluence) including security settings.
* Scheduled repository backups.
* Import/Export and backup to standard Maven 2 file-based repositories.
* Configuration can be dynamically reloaded in runtime from the UI. No need to restart.

Thank you for your effort compiling those facts.

]]> By: Anonymous http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-43 Anonymous Thu, 13 Mar 2008 01:44:31 +0000 http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-43 It would be nice if you can also add sample working configuration which utilizes multiple repositories. I am struggling to get either proximity or archiva working in my setup which access around 10 different maven repos. I couldn't find any sample configuraiton that I could refer to and get the things working. It would be nice if you can also add sample working configuration which utilizes multiple repositories. I am struggling to get either proximity or archiva working in my setup which access around 10 different maven repos. I couldn’t find any sample configuraiton that I could refer to and get the things working.

]]> By: James http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-12 James Thu, 24 Jan 2008 07:52:59 +0000 http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-12 You're kidding right?<br /> <br /> Archiva's web interface is comprised of JSP's.  The first time you visit any page withing Archiva's UI, a JSP needs to be compiled.  Once this is done, the pages subsequently load much faster.<br /> <br /> We've been using Archiva for a couple months now (since 1.0), and with 20 to 30 developers have seen anything but a performance issue.  Downloads for cached or internal artifacts are so fast, they aren't worth benchmarking.  We use an Athlon X2 2.4gz box running RedHat and share it with CVS and Subversion and there has never been an issue for any of our Maven2 developers.<br /> <br /> The only thing that is slow, is Subversion, but that's probably because it has a lot more to do.<br /> <br /> -James You’re kidding right?

Archiva’s web interface is comprised of JSP’s.  The first time you visit any page withing Archiva’s UI, a JSP needs to be compiled.  Once this is done, the pages subsequently load much faster.

We’ve been using Archiva for a couple months now (since 1.0), and with 20 to 30 developers have seen anything but a performance issue.  Downloads for cached or internal artifacts are so fast, they aren’t worth benchmarking.  We use an Athlon X2 2.4gz box running RedHat and share it with CVS and Subversion and there has never been an issue for any of our Maven2 developers.

The only thing that is slow, is Subversion, but that’s probably because it has a lot more to do.

-James

]]> By: Anonymous http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-11 Anonymous Wed, 23 Jan 2008 09:05:16 +0000 http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-11 It's really an understatement to say that Archiva performance leaves something to be desired.   Loaded it up on a powerful test machine, hit the browse button, and I got an hourglass for the next 5 minutes!    Most of the other buttons do the same.   If a fresh repository has this poor performance, what will it be when I load a few thousand snapshots in there?   Too scary to consider. It’s really an understatement to say that Archiva performance leaves something to be desired.   Loaded it up on a powerful test machine, hit the browse button, and I got an hourglass for the next 5 minutes!    Most of the other buttons do the same.   If a fresh repository has this poor performance, what will it be when I load a few thousand snapshots in there?   Too scary to consider.

]]> By: greg http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-10 greg Wed, 12 Dec 2007 09:45:29 +0000 http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-10 How would that popularity concept work, given that the proxy would only be queried when developers dont have a copy of the artifact in their local repos yet? It would also probably show wrong value if certain developers tend to cleanup their local repos :) How would that popularity concept work, given that the proxy would only be queried when developers dont have a copy of the artifact in their local repos yet? It would also probably show wrong value if certain developers tend to cleanup their local repos :)

]]>