I’m not sure that “every end user” feels that this is an issue, and I’m still struggling to understand why splitting a monolithic artifact into several separate modules would ever be considered a minor update.
But, hey. I have popcorn… Later, Andy From: Vladimir Sitnikov <[email protected]> Date: Wednesday, 5 November 2025 at 15:24 To: Maven Developers List <[email protected]> Subject: Re: Proposal: Honor dependencyManagement in intermediate POMs for better version alignment >depMgt and dependencies block Those are workarounds as they would imply every end user would have to manually perform coordinated changes to deps/depMgt sections. Which is exactly the issue I mention *Claim (what I’m showing)With Maven 4 today, a library author cannot safely split a monolithic artifact into several modules andrelease it as a backward-compatible minor version (e.g., 1.1.0) without coordinated changes in downstream applications.* The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.
