Hey, as I see a lot of improvements and (ofc after the initial time effort of the set up) time savings in the future (by not writing the same multiple times but also to avoid introducing manual issues when you do the same for th x times, but always a slightly different cause of the slightly different codes, I'm for this move forward.
Only thing I'm not sure about is the name "maven-core" for me as a fresh guy here always relates to the maven core application but not the plugins - I guess you mean the core basic plugins, but maybe a different name like idk (names...) maven-general-plugin-lib or something (tried to avoid "common"). Greetings Matthias P.S. Yes I've read all the discussion so far. I don't see the issue of competing standards or "old" plugins. It's natural to deprecate and bury old stuff in favor for new - that's somehow the core (haha) message of Maven 4 for me. Or as I call it "Maven 4 is project jigsaw for Maven" Am 15.08.2024 um 13:13 schrieb Tamás Cservenák:
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
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
