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="" />

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

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

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

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

 <target name="build" depends="-download-ivy,clean,compile">
  <mkdir dir="${build.dir}" />
  <javac srcdir="${src.dir}" destdir="${build.dir}" classpathref="runtime.path" />
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?

Popular posts from this blog

One page Stock

Alright.. That was a long absence. The whole last week I dint blog. I dint go away. I was "occupied". I was learning stock trading. Its very fascinating. I have a good weeeked blog for you all. Here is my experience. I can literally hyper-link every word from the following paragraphs, but I am writing it as simple as I can so you can look up the italicised words in wikipedia . I got a paper trading account from a brokerage firm . You need one brokerage account first. Then it can be an Equity account where all your money is yours or a Margin account , where some of the money is lent by the brokerage firm. Then I get Buying power , which is the dollor value of how much stocks you can buy. I can make profit by simple rules. Buy when Price is low. Sell when price is high. There is another more intersting way of earning money. Selling short . Thats when price is not high, per say, but when are confident that the price WILL go down. then buy back when its lowest. This is what

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

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>