Comments on: The Hype About Repository Managers http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/ Thoughts to ponder.. Thu, 24 Jul 2008 02:14:54 +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-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 :)

]]> By: Deng Ching http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-9 Deng Ching Wed, 12 Dec 2007 09:38:26 +0000 http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-9 Thanks for all your suggestions Alex! =) The new features you've mentioned look good. Please feel free to post them up on the dev list so everyone in the community can also give their input. See you in planet Archiva! Thanks for all your suggestions Alex! =) The new features you’ve mentioned look good. Please feel free to post them up on the dev list so everyone in the community can also give their input. See you in planet Archiva!

]]> By: Alex Mayorga Adame http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-8 Alex Mayorga Adame Thu, 29 Nov 2007 23:52:23 +0000 http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/#comment-8 First of all kudos on the release to everyone.<br /> <br /> I've found the "importing", given the confusion I'd propose to change that to "management", of an already existing repository on the file system to be functional and very straight forward.<br /> I've just being using standalone Archiva for a couple of days now and I have some suggestions.<br /> <ul> <li>When browsing repositories it would be nice to have a tidbit on the artifact info page telling me where from is the artifact being pulled (currently I find myself  hovering the pointer over the jar/pom icons to find that out)</li> <li>Also on the info page of the artifacts it shows the "organisation" as a number, shouldn't it show the actual name of the org name.</li> </ul> I've talked on IRC about a "feature" that is needed in the enterprise, even before notifications:<br /> <ul> <li>Approvals (in my experience the enterprise is all about approvals,  tons of them). I've talked on IRC about the waiting room concept, when an "unapproved" artifact is requested over a proxy connector it might be recorded and then when a number of approvals are gathered (architects, legal, tech lead, etc) either by the web interface, mail or whatever means, next time it's requested it would be actually pulled from the proxied repository.</li> <li>Popularity (so management can see what is popular among developers). Maybe even the number of request of an artifact on the "waiting room" (see above) so they can asses that needs more promptly.</li> </ul> I guess with the right guidance I might try to hack my suggestions myself and get to know Archiva from the inside out.<br /> <br /> Thanks again and keep up the excellent work. First of all kudos on the release to everyone.

I’ve found the "importing", given the confusion I’d propose to change that to "management", of an already existing repository on the file system to be functional and very straight forward.
I’ve just being using standalone Archiva for a couple of days now and I have some suggestions.

  • When browsing repositories it would be nice to have a tidbit on the artifact info page telling me where from is the artifact being pulled (currently I find myself  hovering the pointer over the jar/pom icons to find that out)
  • Also on the info page of the artifacts it shows the "organisation" as a number, shouldn’t it show the actual name of the org name.

I’ve talked on IRC about a "feature" that is needed in the enterprise, even before notifications:

  • Approvals (in my experience the enterprise is all about approvals,  tons of them). I’ve talked on IRC about the waiting room concept, when an "unapproved" artifact is requested over a proxy connector it might be recorded and then when a number of approvals are gathered (architects, legal, tech lead, etc) either by the web interface, mail or whatever means, next time it’s requested it would be actually pulled from the proxied repository.
  • Popularity (so management can see what is popular among developers). Maybe even the number of request of an artifact on the "waiting room" (see above) so they can asses that needs more promptly.

I guess with the right guidance I might try to hack my suggestions myself and get to know Archiva from the inside out.

Thanks again and keep up the excellent work.

]]>