Maven 2 & 3

Why incremental build is not supported natively by Maven?

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

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

Bug - A problem which impairs or prevents the functions of the product. MNG-5039 Maven does not properly track class files to be included in jar/test breaking incremental build

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Wendy Smoak added a comment -

You might want to re-post this on the mailing list (or search the archives – I think it's come up before).

Show
Wendy Smoak added a comment - You might want to re-post this on the mailing list (or search the archives – I think it's come up before).
Hide
Permalink
Yegor Bugayenko added a comment -

Actually the problem is related not only to multi-module projects. In general Maven doesn't use plugins incrementally, as I understand.

Show
Yegor Bugayenko added a comment - Actually the problem is related not only to multi-module projects. In general Maven doesn't use plugins incrementally, as I understand.
Hide
Permalink
Jörg Schaible added a comment -

It is more a problem of the plugins and the concept of plugins itself. The Maven core has no idea about the processed files and the actual result. Some plugins work implicitely incremental (compiler plugin using javac, because javac works this way), others are more ignorant (xmlbeans plugin generates the Java files always). So it seems better to create issues for the individual plugins to be more "intelligent" at detecting changes. E.g. the jar plugin does not have to run if the produced jar file is newer than anything that has to be collected. In case of the surefire plugin it is not so easy: It might omit the tests if all test reports are newer than anything in the classes or test-classdes folder, but it has also to check that no dependency has been updated ...

Show
Jörg Schaible added a comment - It is more a problem of the plugins and the concept of plugins itself. The Maven core has no idea about the processed files and the actual result. Some plugins work implicitely incremental (compiler plugin using javac, because javac works this way), others are more ignorant (xmlbeans plugin generates the Java files always ). So it seems better to create issues for the individual plugins to be more "intelligent" at detecting changes. E.g. the jar plugin does not have to run if the produced jar file is newer than anything that has to be collected. In case of the surefire plugin it is not so easy: It might omit the tests if all test reports are newer than anything in the classes or test-classdes folder, but it has also to check that no dependency has been updated ...

People

  • Assignee:
    Unassigned
    Reporter:
    Yegor Bugayenko
Vote (7)
Watch (6)

Dates

  • Created:
    Updated: