As an outsider I would welcome that especially if it (1) made it simpler to write new plug-ins and/or (2) I would get new features or bug fixes "for free" if my plug-ins reused the right superclass or class.
2c, Gary On Thu, Aug 15, 2024, 7:15 AM Tamás Cservenák <ta...@cservenak.net> wrote: > Howdy, > > as am going over multiple plugins (as it is time to upgrade parent, some > bugfix, etc), all I see is: > * a LOT of code duplication across plugins (some even have comments like in > plugin X "this should be shared with Y") > * some "forcefully" pushed out "shared" artifact to share them across > * just many too small codebases that needs a LOT of process/work effort for > small gain > * it is all chopped up into relatively small pieces > > Hence, we were already discussing this idea on Slack: what if we introduce > maven-core-plugin? > > One single plugin that contains some "most common" Mojos? > (nothing new under Sun, this would be the "a la Takari Lifecycle" > situation, where one plugin delivers most common Mojos -- although there > the incentive was build avoidance/incremental build). > > For start, we could consider all 'core' plugins (those referenced from > maven like in lifecycle mapping) except: > * m-compiler-p > * m-surefire-p > > as they are complex on their own. > > WDYT? > Tamas >
