[MCOMPILER-205] incremental compilation broken for package-info classes

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1
• Fix Version/s: 3.10.0
• Assignee: Guillaume Nodet
• Reporter: Lukas Fryc
• Created: 17/Apr/13 08:10
• Updated: 07/Apr/22 17:37
• Resolved: 07/Feb/22 02:04

Description

When we do clean -> compile -> compile, all Java sources are re-compiled for second compilation steps:

[framework]$ mvn clean
...
[framework]$ mvn compile
...
[INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @ richfaces-framework ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 915 source files to /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
...
[framework]$ mvn compile
...
[INFO] --- maven-compiler-plugin:3.1:compile (precompile-sources-for-cdk) @ richfaces-framework ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 915 source files to /mnt/workspace/workspaces/richfaces/richfaces5/framework/target/classes
...

The source code of the affected project: https://github.com/richfaces/richfaces5/tree/077dcfc0a46d03d7ba9a7ac3e701a4adfb834c71

Issue Links

• causes: MCOMPILER-485 Incorrect internal string format in generated package-info.class files on Windows
• is duplicated by: MCOMPILER-368 package-info.java always triggers recompilation of module
• is related to: MCOMPILER-368 package-info.java always triggers recompilation of module
• is related to: MCOMPILER-194 Strange effects with springs @Configurable (AspectJ) and new compiler plugin version 3.0
• is related to: MCOMPILER-187 incremental stuff detect changes even if nothing has changed means too much compilation
• relates to: FLINK-8847 Modules containing package-info.java are always recompiled
• links to: GitHub Pull Request #3
• links to: GitHub Pull Request #88