[
http://jira.codehaus.org/browse/MNG-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243119#action_243119
]
Joerg Schaible commented on MNG-4885:
-------------------------------------
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 ...
> Why incremental build is not supported natively by Maven?
> ---------------------------------------------------------
>
> Key: MNG-4885
> URL: http://jira.codehaus.org/browse/MNG-4885
> Project: Maven 2 & 3
> Issue Type: New Feature
> Reporter: Vincenzo Mancini
>
> 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:
> {noformat}
> foo.jar depends on:
> abc.java
> cde.java
> bar.jar depends on:
> xxx.java
> {noformat}
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
