You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gili (JIRA)" <ji...@apache.org> on 2018/12/16 05:45:02 UTC
[jira] [Commented] (MCOMPILER-368) package-info.java always
triggers recompilation of module
[ https://issues.apache.org/jira/browse/MCOMPILER-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722398#comment-16722398 ]
Gili commented on MCOMPILER-368:
--------------------------------
I found FLINK-8847 which explains what is happening:
{quote}To detect modified files the compiler compares timestamps of the source and .class file. In the case of {{package-info.java}} no .class file is created if *it doesn't contain annotations*, which the compiler interprets as a missing .class file.
{quote}
*Expected behavior*: maven-compiler-plugin should emit some additional metadata to prevent needless recompilation in this case.
> package-info.java always triggers recompilation of module
> ---------------------------------------------------------
>
> Key: MCOMPILER-368
> URL: https://issues.apache.org/jira/browse/MCOMPILER-368
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.8.0
> Environment: Microsoft Windows [Version 10.0.17763.194]
> Maven 3.6.0
> maven-compiler-plugin 3.8.0
> Reporter: Gili
> Priority: Major
> Attachments: testcase.zip
>
>
> # Unzip testcase
> # Run: mvn install
> # Notice that maven-compiler-plugin always claims package-info.java is stale and forces recompilation of entire module
> When package-info.java is present in large modules build times suffer noticeably.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)