Am 12/29/16 um 02:41 schrieb Christian Schulte: > Am 12/29/16 um 02:36 schrieb Christian Schulte: >> Am 12/29/16 um 00:41 schrieb Michael Osipov: >>> If this is how it should (I am neither pro nor cons) work, we should >>> deprecate this element or at least put a big WARNING on it. >> >> We should spit out a big fat warning whenever someone overrides hers/his >> own management. It shouldn't even be possible to do so. That's not a >> feature :-) > > Ask a manager about that. Management is dominant. It should not be > possible to override that anywhere. The resolver should really override > direct dependencies with the management as well and not just transitive > ones. It currently does not only to not break this "feature".
Maybe more technically: Suppose the maven-plugins parent would manage versions of various components. Maven core, plexus archiver, plexus-utils, etc. This must be applied to all plugins using that parent no matter what a plugin declares itself. The author of that parent and the author of a plugin's POM are different persons. Maybe the parent can only be released by a PMC member and plugins can be released by committers etc. Allowing to override the management really is a bad idea. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
