Apache Maven Build Automation Framework

An Apache Maven Build Automation Framework is a build automation system.

• Context:
  • It can (typically) be use to manage Maven-based Projects (described in POM XML files).
  • It can (often) be used for Java-based Projects.
  • …
• Example(s):
  • Maven, v3.6.3, ~2019-11-25.
  • Maven, v2.2.0, ~2009-06-30.
  • Maven, v1.0, ~2019-11-25.
  • …
• Counter-Example(s):
  • SBT Build Automation Framework.
  • Bazel System.
• See: Make (Software), Project Object Model, Unit Testing, Convention Over Configuration, Apache Ant, Jenkins System.

---

---

References

2019

• https://maven.apache.org/what-is-maven.html
  • QUOTE: ... Maven’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, Maven deals with several areas of concern:
    • Making the build process easy
    • Providing a uniform build system
    • Providing quality project information
    • Encouraging better development practices

2018

• (Wikipedia, 2018) ⇒ https://en.wikipedia.org/wiki/Apache_Maven Retrieved:2018-8-14.
  • Maven is a build automation tool used primarily for Java projects.

    Maven addresses two aspects of building software: first, it describes how software is built, and second, it describes its dependencies. Unlike earlier tools like Apache Ant, it uses conventions for the build procedure, and only exceptions need to be written down. An XML file describes the software project being built, its dependencies on other external modules and components, the build order, directories, and required plug-ins. It comes with pre-defined targets for performing certain well-defined tasks such as compilation of code and its packaging.

    Maven dynamically downloads Java libraries and Maven plug-ins from one or more repositories such as the Maven 2 Central Repository, and stores them in a local cache. This local cache of downloaded artifacts can also be updated with artifacts created by local projects. Public repositories can also be updated.

    Maven can also be used to build and manage projects written in C#, Ruby, Scala, and other languages. The Maven project is hosted by the Apache Software Foundation, where it was formerly part of the Jakarta Project.

    Maven is built using a plugin-based architecture that allows it to make use of any application controllable through standard input. Theoretically, this would allow anyone to write plugins to interface with build tools (compilers, unit test tools, etc.) for any other language. In reality, support and use for languages other than Java has been minimal. Currently a plugin for the .NET framework exists and is maintained, and a C/C++ native plugin is maintained for Maven 2.

    Alternative technologies like Gradle and sbt as build tools do not rely on XML, but keep the key concepts Maven introduced. With Apache Ivy, a dedicated dependency manager was developed as well that also supports Maven repositories.

2017

• https://javarevisited.blogspot.com/2015/01/difference-between-maven-ant-jenkins-and-hudson.html
  • QUOTE: What is difference between Maven, ANT, Jenkins and Hudson?

    In short, though Maven and ANT are build tool but main difference is that maven also provides dependency management, standard project layout and project management. On difference between Maven, ANT and Jenkins, later is a continuous integration tool which is much more than build tool. You can setup your CI environment using Jenkins or Hudson and automatically build, test and deploy your Java project. Now last, main difference between Jenkins and Hudson, both are originate from same source code but one is closed source while other is open source.

---