[
https://issues.apache.org/jira/browse/MCOMPILER-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642039#comment-16642039
]
Robert Scholte commented on MCOMPILER-278:
------------------------------------------
First create an issue for it at
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20component%20%3D%20maven-shared-incremental
Next fork https://github.com/apache/maven-shared-incremental/ for the
implementation.
Ps. for the coming period I have several conferences, so that'll claim some
time, meaning it might take some time before responding.
> 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
> Priority: Major
> Attachments: maven-compiler-checksum.patch,
> maven-compiler-plugin-3.1.patch, sampleProject.zip
>
>
> 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
(v7.6.3#76005)
