[ 
https://issues.apache.org/jira/browse/MCOMPILER-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15579818#comment-15579818
 ] 

Robert Scholte commented on MCOMPILER-278:
------------------------------------------

Please provide a new patch (attach it as file) and only change code related to 
this issue. It is now impossible to see what's actually done. An 
integration-test would help, but that's probably hard to create in this case, 
one of use will help with that.

> Incremental build does not track inter-module dependencies.
> -----------------------------------------------------------
>
>                 Key: MCOMPILER-278
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-278
>             Project: Maven Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 3.1
>            Reporter: Michael Zav'yalov
>
> When useIncrementalCompilation=true the plugin actually assumes that this 
> incremental compilation is supported by compiler itself (I state it because 
> of all source files are always sent to compiler).
> But plugin provides an additional optimization - it can detect that there are 
> no changes at all, so calling compiler can be skipped. It is especially 
> critical for javac that does not support incremental build since 1.3.
> Unfortunately, plugin ignores claspath dependencies that are not directory, 
> i.e. - jars, so when dependent jar is modified (in incompatible way) - our 
> project is not re-compiled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to