You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2022/02/03 10:56:00 UTC
[jira] [Updated] (MCOMPILER-483) Stale files detection wrongly detect package-info.java as stale
[ https://issues.apache.org/jira/browse/MCOMPILER-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated MCOMPILER-483:
--------------------------------------
Description:
This happens when the package-info.java only contains some javadoc. In these cases, no class is generated by the compiler and the plugin thus thinks that the class file has been deleted or is not uptodate. This cause the jar to be rebuilt and can cause lots of downstream compilation in reactor projects.
A workaround is to exclude those java files from the compilation process, but that's really not a good idea.
> Stale files detection wrongly detect package-info.java as stale
> ---------------------------------------------------------------
>
> Key: MCOMPILER-483
> URL: https://issues.apache.org/jira/browse/MCOMPILER-483
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Reporter: Guillaume Nodet
> Priority: Major
>
> This happens when the package-info.java only contains some javadoc. In these cases, no class is generated by the compiler and the plugin thus thinks that the class file has been deleted or is not uptodate. This cause the jar to be rebuilt and can cause lots of downstream compilation in reactor projects.
> A workaround is to exclude those java files from the compilation process, but that's really not a good idea.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)