ivy

I'm completely at loss how the ant task ivy:publish is supposed to work. I would expect that I do my normal build, which creates a bunch of jar files, then I would push those jars to the (local) repository. How can I specify from where to retrieve the built jars, and how would those end up in the repository? Update: <target name="publish-local" description="--> Publish Local"> <ivy:retrieve /> <ivy:publish resolver="local" pubrevision="${release.version}" status="release" update="true" overwrite="true"> <artifacts pattern="${dist.dir}/[organisation]-[module].[ext]" /> </ivy:publish> </target>

does anyone knows how do I specify in Ivy something like mirror/mirrorOf in Maven? I'm working with a local Maven proxy (Nexus) and need the tool to specify which of the parent repositories should Nexus proxy be accessing. In Maven I do simply: <mirrors> <mirror> <id>central-mirror</id> <mirrorOf>central</mirrorOf> <url>http://localhost:8081/content/repositories/central</url> </mirror> </mirrors> but I can't find this kind of option in Ivy. I don't think such an option exists directly. You could try implementing a chain , and put your Nexus repository ahead of central in that chain. If I

Is there any possibility to use local Maven repository (~/.m2) as local Ivy cache (~/.ivy)? They have different layouts. Sometimes I use Maven and sometimes I use SBT which uses Ivy underneath, so I have 2 copies of same libs in both Maven and Ivy. I would like to use same dir thus saving disk space and network. Thanks. You can specify the cache and the layout of the cache by using the <cache/> Tag . I think you will have to alter the patterns for the artifacts/ivy.xml files. The Tag is described here: http://ant.apache.org/ivy/history/2.0.0/settings/caches.html . It seems that it should work,

I was wondering about the best way to manage projects dependencies from ant. What are the pros and cons of the Maven Ant task and of Ivy? Chris Since what you're wanting to do is add dependency management to an existing Ant project, that's precisely what Ivy's designed to do. Dependency management is a big part of Maven, but far from all of it. Maven is more of a project-oriented tool that does several other things in addition to dependencies. It would be worth considering if you were planning to migrate to Maven and use additional Maven features as well, but it's a bit much if all you'd use

Quick resolution The required credential expects the exact realm as defined by nexus. See below how to find the one you have defined, but most certainly is "Sonatype Nexus Repository Manager". Add the rest of the details to the credentials as normal. c:/data/user/.sbt/.credentials realm=Sonatype Nexus Repository Manager host=nexus user=repouser password=password build.sbt credentials += Credentials(Path.userHome / ".sbt" / ".credentials") publishTo <<= version { v: String => val nexus = "http://nexus/" if (v.trim.endsWith("SNAPSHOT")) Some("snapshots" at nexus + "content/repositories/libs

Compile times are slowed by 4s resolving dependant libs for my javac step every build on this line: <target name="compile" depends="bootstrap"> <ivy:cachepath pathid="classpath"/> <!-- SLOW --> I want to essentially CACHE the results of ivy:cachepath so I don't have to do it every build. I want ${classpath} to exist in less than 0.2 seconds Context: This is a vanilla ant build.xml which bootstraps ivy, uses an ivy.xml file that lists standard maven dependencies, then calls javac with those libs in a class path) <property name="ivy.install.version" value="2.4.0"/> <property name="ivy.jar.dir"