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 retrieve best use practice?

Thanks Marc. Anybody else have suggest? Jammy 2015-11-04 15:59 GMT+08:00 Marc De Boeck : > We are using the second approach: use Ivy classpath to compile. > For me it is the most efficient and elegant way to work with Ivy and the > Ivy-cache. > > Regards, > Marc > > > >

IVY Clearcase integration

Dear IVY users, developers, My project are source controlled with Clearcase, I built the shared repository, do anybody have suggest where the shared repository should be allocate? I thought I can check-in to clearcase and user should not manually donwload this folder, in IVY we have customized

Re: IVY retrieve best use practice?

On 04.11.2015 07:46, Jammy Chen wrote: We have used ivy:cachepath for our compiles, test-runtime, but since we had a lot of troubles on IVY 2.3.x and also with the IvyDE we decided to switch to a folder based ivy:retrieve. Also we are using a very simplistic eclipse plugin to reference all libs

Re: IVY retrieve best use practice?

We are using the second approach: use Ivy classpath to compile. For me it is the most efficient and elegant way to work with Ivy and the Ivy-cache. Regards, Marc 2015-11-04 7:46 GMT+01:00 Jammy Chen : > Hello IVY users/developers, > > I am now immigrating my project to with

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