Geeth Narayanan

Subscribe to Geeth Narayanan: eMailAlertsEmail Alerts
Get Geeth Narayanan: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

Top Stories by Geeth Narayanan

In part one of this article we discussed the core competencies of Maven and how it fits into application development and build management. Now we'll delve into some of the practicalities in exercising Maven using a practical example that will walk you through some of the common tasks encountered in typical project development and how they can be done using Maven. Downloading & Installing Maven The latest version of Maven 2 can be downloaded at, Maven's official site. When this article was written, Maven 2.0.6 was the latest version available. It can be downloaded and installed following these steps: 1.  Download the appropriate binary file 2.  Unarchive the binary file and install it in a local directory 3.  Add a maven2InstallationDirectory/bin directory to the system PATH variable 4.  By default, Maven 2 uses ~/.m2/repository as i... (more)

An Introduction to Maven - Part III

In the parts 1 and 2 of this article, we demonstrated how to download and install Maven 2, how to install the Maven 2 plugin for Eclipse, and how to go about setting up a project directory structure using Maven 2. We used a simple use case for displaying employee details on the Web given an employee ID, but deliberately made the design a bit complex by introducing design concepts such as XML binding, EJBs, and JCA connectors to illustrate a few of the many features offered by Maven. In this final installment of the article, we continue with the remaining modules in our example an... (more)

An Introduction to Maven - Part I

Maven is a promising application development lifecycle management framework coming from Apache's armory of open source tools. Maven was originally developed as a framework to manage and mitigate the complexities of building the Jakarta Turbine project and soon became a core entity of the Apache Software Foundation project. Without a uniform application development lifecycle management framework, different development teams would create their own build frameworks with varying flavors and complexity and this tendency would only proliferate as more and more new projects get develop... (more)