Am 11/17/16 um 23:56 schrieb Christian Schulte: > Am 11/15/16 um 23:41 schrieb Jason van Zyl: >> Almost none of the changes are well documented, there’s no release notes, >> we’ve told you to roll back or stop making behavioral changes.
Put another way. Please take a look at the following constants in current master DefaultModelBuilder. If you say roll back, you can do that yourself easily by updating those constants to look like: DEPENDENCY_MANAGEMENT_IMPORT_VERSION_RANGES = false; DEPENDENCY_MANAGEMENT_IMPORT_EXCLUSIONS = false; DEPENDENCY_MANAGEMENT_IMPORT_RELOCATIONS = false; DEPENDENCY_MANAGEMENT_IMPORT_INHERITANCE_PROCESSING = false; No more system properties and the model builder will not change behavior any more. The last property has been requested to default to 'true'. In JIRA, on users@ by independent parties. Just set all those constants to false and things are rolled back. My proposal is to make the DEPENDENCY_MANAGEMENT_IMPORT_INHERITANCE_PROCESSING property a POM property 'maven.model.dependencyManagementImportInheritanceProcessing'. If that property is 'true', import scope of *that* POM will be processed differently. Older Maven versions do not understand that property, of course. No way - don't do that? Just set that constant to false and be done with it. I need to update the JIRA issue once more telling those guys that it will not be part of 3.4 or any other 3.x Maven version because it won't pass a release vote. Case closed. Just say: "Don't do it that way because older Maven versions would start building a different effective model than more recent Maven versions" and the next commit will set it to false once and for all. Someone wanting it, can patch Maven himself and use that patched version. It's easy based on what we now have on master. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
