[
https://issues.apache.org/jira/browse/MCOMPILER-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839883#comment-17839883
]
ASF GitHub Bot commented on MCOMPILER-515:
------------------------------------------
desruisseaux commented on PR #160:
URL:
https://github.com/apache/maven-compiler-plugin/pull/160#issuecomment-2071095574
> I can tell you with 100% certainty that only tracking file timestamps
won't work and will be a bug farm.
It is incomplete, but this is what the current plugin and the `javac`
command line do. Implementing a better incremental build would probably be a
multi-steps process. In medium term, my goal is to migrate the plugin from
Maven 3 / Plexus API to Maven 4 / `javax.tools` API in order to improve JPMS
support. Fixing some of the incremental build issues is a side effect of this
work. The goal for now is only to preserve the existing functionalities (with
bug fixes).
After a refactored compiler plugin become stable enough, it would be
possible to investigate how to do better. The proposal to use comma-separated
values in `incrementalCompilation` parameters leaves room for that.
> Plugin is NOT incremental, so let it go
> ---------------------------------------
>
> Key: MCOMPILER-515
> URL: https://issues.apache.org/jira/browse/MCOMPILER-515
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Reporter: Tamas Cservenak
> Priority: Major
>
> The maven-compiler-plugin is NOT incremental, so we should just let it go.
> The shared incremental stuff is broken since it's last factual code change
> (2012!).
> Moreover, the broken incremental stuff just makes us look bad, see the "mvn
> clean install" vs "mvn verify" issue:
> [https://www.youtube.com/watch?v=XeQj-IbSxJI]
> Accept it, that this plugins is not incremental, so it should not make users
> believe it is. Moreover, the bugs in this feature exist for too long, that
> just cause harm to users and to project as whole.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
