Skip to main content

Apache maven incremental build

Apache maven is one of the popular tool for building and managing java projects. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information.
However when you have projects with multiple modules, it follows some issue when you compiling your project. One of them is incremental building, which means when you updates your project from the version control, you have to build the entire system by command mvn clean install. Consider the following maven project structure:
IncrementalBuild
|_ _ test-api
|_ _ test-api-impl
|_ _ test-donothing
where module test-api-impl dependent on module test-api. Whenever we will make some change on module test-api, we have to recompile and build the module test-api-impl.
If we will enter the command mvn install module test-api-impl will not get the updated version from the module test-api. You have to run command mvn clean install which will rebuild the entire project. Sometime it's time consuming and just unnecessary. You can download the project from here and check your self.
Apache maven currently doesn't support for the incremental build even on version 3.0.3.
But there is a plugin called Maven-Incremental build plugin, which can build project incrementally.
Just add the following plugin in the root pom file and you are ready for go
<plugin>
 <groupId>net.java.maven-incremental-build</groupId>
 <artifactId>incremental-build-plugin</artifactId>
 <version>1.4</version>
 <executions>
  <execution>
   <goals>
   <goal>incremental-build</goal>
   </goals>
  </execution>
 </executions>
</plugin>
Now you can run mvn install without goal clean and the project will detects the updated code and recompile modules if need.
UPD:- Note that, following page http://maven-incremental-build.java.net/site/usage.html contains incorrect groupId on example "net.java.incremental-build-plugin" which will not uploaded on central maven repository.
Resource:
1) Apache Maven Incremental Build support for WSO2 Carbon
2) Apache maven incremental plugin mojo

Comments

Popular posts from this blog

Apache Ignite deep dive, SQL engine

Apache Ignite  is an open source memory-centric distributed database, caching and comput- ing platform. From the beginning, it was designed as an in-memory data grid for developing a high-performance software system. So, it’s core architecture design is slightly different from the traditional NoSQL databases, which can simplify building modern applications with a flexible data model and simpler high availability, high scalability.     Moreover, to understand how to design application with any databases or framework properly, you must understand the architecture of the database or framework itself. By getting a better idea of the system, you can solve different problems in your enterprise architecture landscape, can select a comprehensive database or framework that is appropriate for your application and get the maximum benefits from the system. In this article we are going to explore the Apache Ignite SQL engine.      Under the hood...

Book review: High Performance in-memory computing with Apache Ignite by Sadruddin Md

A new title  The Apache Ignite book  has been released including Ignite 2.6 and above. Read the full book review by Sadruddin Md .

Quick start with In memory Data Grid, Apache Ignite

UP1: For complete quick start guide, see also the sample chapter of the book "High performance in-memory computing with Apache Ignite" here . Even you can find the sample examples from the GitHub repository . IMDG or In memory data grid is not an in-memory relational database, an NoSQL database or a relational database. It is a different breed of software datastore. The data model is distributed across many servers in a single location or across multiple locations. This distribution is known as a data fabric. This distributed model is known as a ‘shared nothing’ architecture. IMDG has following characteristics: All servers can be active in each site. All data is stored in the RAM of the servers. Servers can be added or removed non-disruptively, to increase the amount of RAM available. The data model is non-relational and is object-based.  Distributed applications written on the platform independent language. The data fabric is resilient, allowing non-disruptive au...