hunterpayne commented on PR #160:
URL:
https://github.com/apache/maven-compiler-plugin/pull/160#issuecomment-2070771711
Great, so we have 2 buckets to break these issues into. 1) issues with the
difference in behavior with javac (vs JDT) and 2) issues with the difference in
behavior with this plugin and the Takari one. I'm curious, what are the issues
in the first bucket? Perhaps the target should be to get the maven compiler to
work on JDT as a requirement instead of javac and JDT. Maybe that's a goal we
can achieve.
On Monday, April 22, 2024 at 12:21:17 PM PDT, Tamas Cservenak
***@***.***> wrote:
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
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
