+1
sounds like a classic example of YAGNI and over-generalization in search of a problem On Sat, Sep 19, 2026 at 11:17 AM Sylwester Lachiewicz <[email protected]> wrote: > > Hi, > > maven-shared-incremental was released once, as 1.1, on 2013-04-03, and has > had no functional change since. Every commit on master after that release > is housekeeping (parent POM bumps, formatting, CI and site descriptor > updates); the 2.0.0-SNAPSHOT on master has never been published. > > The library has a single consumer: maven-compiler-plugin. The 4.x line > dropped it in 2024 with its own IncrementalBuild implementation, and > https://github.com/apache/maven-compiler-plugin/pull/1128 > <https://www.google.com/url?q=https://github.com/apache/maven-compiler-plugin/pull/1128&source=gmail&ust=1789917106312000&sa=E> > inlines the two classes into the 3.x line, keeping the target/maven-status > layout and file formats unchanged. Once that is merged, no Maven project > depends on the library. The abstraction was never picked up by any other > plugin in the 13 years since it was extracted. > > I therefore propose that we retire maven-shared-incremental. > > I do not propose a final release. 1.1 stays available on Maven Central, and > the open items on the repository (PR #23 and two issues, MSHARED-767 and > MSHARED-1262) will be closed with a pointer to the compiler plugin, which > already carries the same fix. > > If this vote is successful I will mark the component as retired on its > site, and the source code repository will be archived, meaning it's > read-only in the future. > > The process for retiring a component is described here: > https://maven.apache.org/developers/retirement-plan-plugins.html > > The vote is open for 72 hours. > > [ ] +1 Yes, it's about time > [ ] -1 No, because... > > Sylwester -- Elliotte Rusty Harold [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
