[
https://issues.apache.org/jira/browse/MCOMPILER-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620925#comment-16620925
]
Robert Scholte commented on MCOMPILER-278:
------------------------------------------
So if I understand correctly this is about a dependency change, not a module
change. The sampleProject is confusing, it should be 2 independent projects.
I'm actually kind of surprised this wasn't implemented yet. I think this is
something that should be solved in the
[maven-shared-incremental|https://maven.apache.org/shared/maven-shared-incremental].
The date of the jars should be compared to some other date, I think using the
date of the target-directory should work. Since [~olamy] wrote
maven-shared-incremental: WDYT? Add this to the shared library?
> 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)
