[
https://issues.apache.org/jira/browse/MCOMPILER-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839826#comment-17839826
]
ASF GitHub Bot commented on MCOMPILER-515:
------------------------------------------
cstamas commented on PR #160:
URL:
https://github.com/apache/maven-compiler-plugin/pull/160#issuecomment-2070735050
Today, if one needs _fully incremental (and build avoidance) with current
stable Maven 3.9.x, one should use Takari Lifecycle plugin_. But even then you
should use Eclipse JDT not javac. But, in turn, with JDT, you get other nice
things like enforcing dependency usage and so on...
http://takari.io/book/index.html
> 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)
