apache / apache/maven-compiler-plugin
[MCOMPILER-515] Plugin is NOT incremental, so let it go
- Dominant language
- Java
- Stars
- 261
- Forks
- 191
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 8
Description
**[Tamas Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)** opened **[MCOMPILER-515](https://issues.apache.org/jira/browse/MCOMPILER-515?redirect=false)** and commented
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.
---
**Issue Links:**
- [MCOMPILER-563](https://issues.apache.org/jira/browse/MCOMPILER-563) Deprecate/rename useIncrementalCompilation
**Remote Links:**
- [GitHub Pull Request #160
](https://github.com/apache/maven-compiler-plugin/pull/160)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked MCOMPILER-563 issue and GitHub pull request #160, then inspect how the maven-compiler-plugin exposes and handles incremental compilation. Done means the plugin no longer presents the broken incremental behavior as supported, with the related option behavior and documentation aligned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100