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 >>

Decorator for Memcache Get/Set in python

I have suggested some time back that you could modularize and stitch together fragments of js and css to spit out in one HTTP connection. That makes the page load faster. I also indicated that there ways to tune them by adding cache-control headers. On the server-side however, you could have a memcache layer on the stitching operation. This saves a lot of Resources (CPU) on your server. I will demonstrate this using a python script I use currently on my site to generate the combined js and css fragments. So My stitching method is like this @memize(region="jscss") def joinAndPut(files, ext): res = files.split("/") o = StringIO.StringIO() for f in res: writeFileTo(o, ext + "/" + f + "." + ext) #writes file out ret = o.getvalue() o.close() return ret; The method joinAndPut is * decorated * by memize. What this means is, all calls to joinAndPut are now wrapped (at runtime) with the logic in memize. All you wa...
Read More >>

Faster webpages with fewer CSS and JS

Its easy, have lesser images, css and js files. I will cover reducing number of images in another post. But If you are like me, You always write js and css in a modular fashion. Grouping functions and classes into smaller files (and Following the DRY rule, Strictly!). But what happens is, when you start writing a page to have these css and js files, you are putting them in muliple link rel=style-sheet or script tags. Your server is being hit by (same) number of HTTP Requests for each page call. At this point, its not the size of files but the number server roundtrips on a page that slows your page down. Yslow shows how many server roundtrips happen for css and js. If you have more than one css call and one js call, You are not using your server well. How do you achieve this? By concatinating them and spitting out the content as one stream. So Lets say I have util.js, blog.js and so.js. If I have a blog template that depends on these three, I would call them in three script tags. Wh...
Read More >>