{"id":1971,"date":"2017-12-07T06:37:27","date_gmt":"2017-12-07T06:37:27","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/?p=1971"},"modified":"2021-11-18T07:10:17","modified_gmt":"2021-11-18T07:10:17","slug":"mavens-objectives","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/mavens-objectives\/","title":{"rendered":"Maven’s Objectives"},"content":{"rendered":"

scmuser created the topic: Maven’s Objectives<\/strong>
\nWhat is the maven main objectives?<\/p>\n

rajeshatbuzz replied the topic: Re:Maven’s Objectives<\/strong>
\nMaven’s primary goal is to allow a developer to comprehend the complete state of a development effort in the shortest period of time. In order to attain this goal there are several areas of concern that Maven attempts to deal with:
\n\u2022 Making the build process easy
\n\u2022 Providing a uniform build system
\n\u2022 Providing quality project information
\n\u2022 Providing guidelines for best practices development
\n\u2022 Allowing transparent migration to new features<\/p>\n

Making the build process easy
\nWhile using Maven doesn’t eliminate the need to know about the underlying mechanisms, Maven does provide a lot of shielding from the details.<\/p>\n

Providing a uniform build system
\nMaven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects.<\/p>\n

Providing quality project information
\nMaven provides plenty of useful project information that is in part taken from your POM and in part generated from your project’s sources. For example, Maven can provide:
\n\u2022 Change log document created directly from source control
\n\u2022 Cross referenced sources
\n\u2022 Mailing lists
\n\u2022 Dependency list
\n\u2022 Unit test reports including coverage
\nAs Maven improves the information set provided will improve, all of which will be transparent to
\nusers of Maven.
\nOther products can also provide Maven plugins to allow their set of project information alongside
\nsome of the standard information given by Maven, all still based on the POM.<\/p>\n

Providing guidelines for best practices development
\nMaven aims to gather current principles for best practices development, and make it easy to guide a
\nproject in that direction.
\nFor example, specification, execution, and reporting of unit tests are part of the normal build cycle
\nusing Maven. Current unit testing best practices were used as guidelines:
\n\u2022 Keeping your test source code in a separate, but parallel source tree
\n\u2022 Using test case naming conventions to locate and execute tests
\n\u2022 Have test cases setup their environment and don’t rely on customizing the build for test
\npreparation.<\/p>\n

Maven also aims to assist in project workflow such as release management and issue tracking.
\nMaven also suggests some guidelines on how to layout your project’s directory structure so that once
\nyou learn the layout you can easily navigate any other project that uses Maven and the same defaults.<\/p>\n

Allowing transparent migration to new features
\nMaven provides an easy way for Maven clients to update their installations so that they can take
\nadvantage of any changes that been made to Maven itself.
\nInstallation of new or updated plugins from third parties or Maven itself has been made trivial for this
\nreason.<\/p>\n\n