Nexus 3.0 due out soon will be including Docker and also some internal changes to make additional repo types easier to add. It current supports npm, ruby, yum, apt, eclipse P2 in addition to maven style repos today. These are all available in the OSS version of Nexus. To get more than just Maven with artifactory, you need to pay, but they are slightly ahead of nexus in repo types supported as they have docker, python, bower, scala and vagrant also currently.
I think Sonatype (nexus) is looking to make their money on the Pro version with higher up the chain features and tools like the license management and security alert type features plus enterprise type support. I actually have both that I'm supporting in my environment . Overall if you just need repo features and not any of these upchain features, I prefer the Nexus implementation. The repos are maintain as a file system of exactly what you see via the browser. Artifactory has its own DB and stores the identity of everything there and maintains the files with like md5sum filenames on the back end. If the DB goes, you are hosed whereas you just need to backup the file system for nexus and a recovered instance can just rebuild indexes. I also prefer the Nexus UI, but YMMV Daniel -----Original Message----- From: Marc De Boeck [mailto:mdeb...@gmail.com] Sent: Thursday, November 05, 2015 4:26 PM To: ivy-user@ant.apache.org Subject: Re: IVY Clearcase integration It's funny, because the reasons why we chose Artifactory, seem to be the same as the reasons why you chose Nexus :) I compared Nexus, Artifactory and Archiva approximately 3 years ago. At that time, I had the impression that Nexus had only support for standard maven repositories, and we were working with customized ivy-repositories. My impression was also that you had to pay for the more interesting features. I may have been wrong then ? Then I installed Artifactory OSS (the free version), and it had also support for Ivy and Gradle builds. Unfortunately, the repository layouts were not configurable in the free version. But I found out that Artifactory still works correctly if the defined layout in Artifactory is different from the layout that the build system uses for publishing and resolving. So it is really Ivy who controls the layout of the repo when you publish and resolve. When I had installed the Artifactory as a POC, it was actually immediately considered as the official binary repository system, and we didn't look anymore at Nexus. Installation of Artifactory was also straightforward, using an rpm package. Also upgrading seems to be as easy as the Nexus upgrades. When we purchased Artifactory, I configured the repository layouts of the repos correctly (which in my opinion didn't make a big operational difference), and we started using the extra features such as better integration with Jenkins, build promotion in Artifactory, RPM and Python repositories. I saw that Artifactory also supports docker, but I assume only in the paid version. If all these features are available in the free Nexus, then Nexus may be a better alternative, but then there are must be other features which are only available in the paid Nexus? Regards, Marc 2015-11-05 16:46 GMT+01:00 hkais...@googlemail.com <hkais...@gmail.com>: > On 04.11.2015 14:41, Marc De Boeck wrote: > >> >> Later on, we moved to Git and to Artifactory. We chose Artifactory >> above Nexus, because we found that Nexus was too much focused on the >> maven eco-system. I am not sure if this is still the case. On the >> other, hand the GUI of Nexus seems to be more intuitive. Anyway, I am >> quite happy with the features and versatility of Artifactory. >> Initially we used the free OSS version, but since last year, we >> purchased the Pro version. >> >> Marc, can you tell me what was the decission against Nexus? > Because we decided against Artifactory since it was forcing us to > switch to commercial version if we do not want only a simple Maven Repository? > > E.g. we use Nexus as Maven & Ivy Repo, along with NPM along with docker. > Right now we are waiting for the new feature to support also bower. > > Also the maintenance of Nexus was easier on our tests (about 18 months > ago). > Nexus was a simple unzip and a start of the shell script. It also was > pretty easy upgrading to new versions, since the repository and the > application was strictly separated. > So the setup took us 10 mins and the upgrade takes most time to create > a backup, before doing the upgrade which takes less than 5 mins. > > Would be great if you could share your experiences. > >
