Skip to main content

Moving on to Ivy.

Maven has its share of success, at the same time it has some shortcomings. Many felt the Idea was right, the implementation was not. There were a few rants too. Project Ivy was started on that note. Today, Everyone is talking about Ivy and How Ivy can fix your woes from maven.

So, I began to test drive Ivy. Ivy has got pretty good documentation. And the edge over maven is, that you dont have to adapt your project to it (like maven). You can make ivy adapt to your project. All you need to start is a jar to put in your ant lib folder. The examples list a mighty hard way of starting with ivy - So I modified a little bit to get it easy and install ivy automatically. Also this can be used as a template build.xml file for starting from scratch :)

<!-- Use namespace even before bootstrap -->
<project xmlns:ivy="antlib:org.apache.ivy.ant" default="build" name="SarathPOC">
 <property file="build.properties" />

 <path id="compile.path">
  <fileset dir="${lib.dir}/compile" />
 </path>
 <path id="runtime.path">
  <path location="${build.dir}" />
  <fileset dir="${lib.dir}/compile" />
  <fileset dir="${lib.dir}/runtime" />
 </path>

 <target name="-download-ivy" unless="skip.download">
  <!-- Download directly (and skip if it exists or if instructed) -->
  <get src="http://repo1.maven.org/maven2/org/apache/ivy/ivy/${ivy.install.version}/ivy-${ivy.install.version}.jar" dest="${ant.library.dir}\ivy.jar" usetimestamp="true" />
 </target>

 <target name="compile" depends="-download-ivy" description="Compile Project, Download Ivy Dependencies">
  <ivy:retrieve pattern="${lib.dir}/[artifact]-[revision].[ext]" />
 </target>

 <target name="clean">
  <delete includeemptydirs="true" failonerror="false">
   <fileset dir="${build.dir}" />
   <fileset dir="${lib.dir}" />
  </delete>
 </target>

 <target name="build" depends="-download-ivy,clean,compile">
  <mkdir dir="${build.dir}" />
  <javac srcdir="${src.dir}" destdir="${build.dir}" classpathref="runtime.path" />
 </target>
</project>
Thats is it, Ivy is installed. If you want to download manually, you can go to the main site. It includes examples.

From here, you could jump start, understand dependency resolution. I am looking at these two for today. However, There is more to Ivy - mainitaing your repositories, Resolvers and Chaining them etc. May be after I get hooked in?
Labels:

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery
Read More >>

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour...
Read More >>

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value> ...
Read More >>