[MNG-4885] Why incremental build is not supported natively by Maven?

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Assignee: Unassigned
• Reporter: Yegor Bugayenko
• Created: 02/Nov/10 14:16
• Updated: 22/Jan/14 20:31
• Resolved: 22/Jan/14 20:31

Description

I have a multi-module project with two sub-modules. I compile and package it without mistakes. The build is complete. Then I make a change in one .java file in one of them. And now I'm trying to package the whole project again. Maven re-runs tests in both two modules, static code analysis in both modules, etc.

Why so? It's a very ineffective way of building, as far as I understand. Maybe maven can introduce a mechanism of "dependency discovery" between files. Like:

foo.jar depends on:
  abc.java
  cde.java
bar.jar depends on:
  xxx.java

When there is a change in cde.java only - maven SHOULD NOT do anything with bar.jar. This is how Unix make utility is working... Thanks.

Issue Links

• is duplicated by: MNG-5039 Maven does not properly track class files to be included in jar/test breaking incremental build