[
http://jira.codehaus.org/browse/MNG-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241854#action_241854
]
Wendy Smoak commented on MNG-4885:
----------------------------------
You might want to re-post this on the mailing list (or search the archives -- I
think it's come up before).
> 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: Bug
> 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
