Skip to main content

Maven - Is it worth the hype?

I am glad I entered a (somewhat) heated argument with a friend of mine about maven and its' usefulness. My stand was that maven saves developers' life. His stand was otherwise. The points I had were, quick start, arch types, version-ing in repo and a good M2 eclipse plugin. My friend however still believes ant is the best thing ever happened to Java community. He would rather deal with the jars himself than excluding every conflicting jar manually. That lead me researching.

For me the selling points in maven are
  • With Maven archetypes, You can create a project (template) in one command. And voila you are good to go. But this is not a very big selling point, because most times, you just create once.
  • Maven also gives you a way to create a project for different IDEs automatically. This one is very nice, coz you need not check in the classpath and project (config) files into your source control. Also, A new user does not need a setup help since the project structure is familiar and IDE is good to start compiling right away (put m2 plugin in place). Especially when people get familiar with the structure. And yes maven had standardized the layout to a big extent.
  • Maven dependency management and transitive dependency resolution is another feature that saves a 1000 lives. This is one thing the impresses me much. And the one thing that my friend disagrees. To an extent I comply with his disagreement. Because as much as the dependency management is impressive. The conflict resolution is very bad! very very bad. However, My first instinct is that, this should not be every time, happens only at the beginning (setup) or when adding a new dependency. So it is still Okay.

Having said all that, I am huge fan of linux, customisation attracts me. Asking my project to *comply* to a set of rules is not really something I would take as a good thing? So do I like ant. Hell yes. What about maven. What do you think? Is it worth the Hype? So far I do think so.
Labels:

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

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