RE: IVY Clearcase integration

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

Re: IVY Clearcase integration

Thanks Marc, I would try Artifactory to see if it fits my case. Jammy 2015-11-04 21:41 GMT+08:00 Marc De Boeck : > I agree mostly with hkaiserl, but I'd like to add some extra thoughts. > > When we started using Ivy, we were also using ClearCase. Initially we > decided to

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

Re: IVY Clearcase integration

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

Re: IVY Clearcase integration

I agree mostly with hkaiserl, but I'd like to add some extra thoughts. When we started using Ivy, we were also using ClearCase. Initially we decided to put 3rd party libraries etc also in ClearCase. Our own built artifacts were stored on a shared drive (not version controlled). This worked not so

Re: IVY Clearcase integration

Clearcase is in my eyes a *source* config management system. Jar files are generated/compiled binaries from sources. So no source repository - also not clearcase - would be a good solution for managing binary configurations. Instead I would stick to a maven repository like sonatype nexus for