[
https://issues.apache.org/jira/browse/MCOMPILER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MCOMPILER-349.
------------------------------------
Resolution: Fixed
Assignee: Robert Scholte
Fix Version/s: 3.8.1
Fixed in
[678360dafc25667d89d1e081270bfbd13b5285f5|https://gitbox.apache.org/repos/asf?p=maven-compiler-plugin.git;a=commit;h=678360dafc25667d89d1e081270bfbd13b5285f5]
Thanks for the patch!
> maven-compiler-plugin does not recompile a module if a dependency module has
> been updated & recompiled
> ------------------------------------------------------------------------------------------------------
>
> Key: MCOMPILER-349
> URL: https://issues.apache.org/jira/browse/MCOMPILER-349
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Reporter: Ahmet Bolac
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.8.1
>
>
> We have two modules A and B, where A depends on B. When running an
> incremental build, we observe that if the sources of A has not changed, but
> sources of B has been changed, module B gets recompiled as expected, but then
> module A is considered up-to-date and not recompiled. If there are any
> breaking changes in module B, we would expect A to fail compilation but it
> does not happen when running an incremental build. We only see A recompile
> after a clean.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)