Understanding The Problems Without Maven And Its Objectives
Posted By : Neha Dahiya | 30-Apr-2018
Introduction
A powerful project management tool based on Project Object Model(POM). It is used to build and manage any kind of Java-based projects. It is used to make the work of Java developers easier and simpler.
Understanding the problem without Maven
Following are the problems discussed below which are faced without Maven:
1) Adding a set of Jars in each project: Set of jar files are to add in each project whether the case of spring, struts or hibernate frameworks. Also, all the dependencies of jars are to be included.
2) Creating the right project structure: Right project should be created in struts or servlet so as to execute it properly.
3) Building and Deploying the project: To make the project work properly, it should be built and deployed properly.
Maven’s Objectives
The primary goal of Maven is to allow a user to comprehend the complete state of a development effort in the shortest period of time.
- Makes the build process easier
- Provides a uniform build system
- Provides quality project information
- Provides guidelines for best development practices
- Allows transparent migration to new features
Lets discuss the objectives in detail:
Making the build process easy:
Maven provides shielding from the details though it doesn’t eliminate the need for knowing the mechanisms underlined.
Providing a uniform build system:
Using POM and its plugins, Maven allows to build its project which can be shared by all projects, thus a uniform build system is built. Once you learn how to build a single project in Maven, automatically you will learn how Maven projects save your immense time while navigating many projects.
Providing quality project information:
Maven provides useful project information which is part of your Project Object Model and is generated from the project’s source. Maven can provide following information:
- List of Dependencies
- Mailing List
- Unit Test Report and its coverage
- Change Log Document.
Maven also improves the information set, also Maven Plugins are provided so as to allow the information along with the standards of Maven based on POM.
Providing guidelines for best practices development:
Maven aims to provide guidelines to gather the principles for the development, and it becomes easy to guide a project according to the direction.
Taking an example, specifications, execution and reporting the unit test cases for a normal build life cycle in Maven
Test source code should be kept in a separate, but in a parallel source tree. Names conventions should be used for location and execution of tests. There should be test case setup environment. Maven also helps in project’s workflow like issue tracking and release management.
Also, Maven provides some guidelines about the layout of the directory structure of the project for easy navigation to other Maven projects with the same defaults.
Allowing transparent migration to new features:
Maven provides easy updations for the installations for the clients so that any changes can be updated easily.
New updations plugins from Maven itself or from the third party are also made trivial for the above reason.
Thanks!!
Cookies are important to the proper functioning of a site. To improve your experience, we use cookies to remember log-in details and provide secure log-in, collect statistics to optimize site functionality, and deliver content tailored to your interests. Click Agree and Proceed to accept cookies and go directly to the site or click on View Cookie Settings to see detailed descriptions of the types of cookies and choose whether to accept certain cookies while on the site.
About Author
Neha Dahiya
Neha is a bright QA Engineer with skills in manual testing . Apart from finding bugs in application, she loves sketching and painting.