You're welcome Curtis, thanks for the discussion! If you want to see a live example of this build structure check Spring-boot on GitHub.
Cheers, S. On Wednesday, 24 August 2016, Curtis Rueden <[email protected]> wrote: > Hi Christian & Stephane, > > Christian Schulte wrote: > > It has never been possible to override a property in the BOM from the > > imorting POM. > > Thanks Christian, I stand corrected! > > So it is a consequence of the fact that my projects' managed dependency > versions previously came in through inheritance, but now (with the new > Maven 3.4.0 behavior) the imported versions always take precedence. > > Stephane Nicoll wrote (in a different thread): > > Your parent would become a parent for pluginsManagement and all the > > dependencyManagement would move to a separate BOM that you would > > manage the same way as the two others. In Spring Boot we have done > > both actually (because we don't have the same requirement that you > > explain here). "spring-boot-dependencies" is the bom and > > "spring-boot-parent" is the parent pom. The latter extends from the > > former. If you use the parent you get everything. If you don't, > > there's still a separate pom that you can use as a BOM. > > Thanks Stephane for this—together with Christian's comment above, it makes > me realize that we will need to use that scheme for our updated POM > structure as well: our pom-base will need to extend our BOM as you say. And > the BOM will need to manage _all_ component versions directly, not via > composition using imports, or else it will not be possible to override > version properties in downstream consumers to change dependency versions. > > Or perhaps that behavior is not so important... but if we stop supporting > it, our community will need some time to get used to it. > > In general, thanks to you both for investing so much time in this > discussion. > > Regards, > Curtis > > -- > Curtis Rueden > LOCI software architect - http://loci.wisc.edu/software > ImageJ2 lead, Fiji maintainer - http://imagej.net/User:Rueden > Did you know ImageJ has a forum? http://forum.imagej.net/ > > > On Wed, Aug 24, 2016 at 12:15 PM, Christian Schulte <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> Am 24.08.2016 um 19:05 schrieb Curtis Rueden: >> > One nuance I do not discuss is how importing a BOM under the new scheme >> now >> > resolves all version properties, such that overriding them in the >> consuming >> > POM has no effect anymore. I still feel this is a bug (or at least >> > undesired quality) of the new approach. >> >> It has never been possible to override a property in the BOM from the >> imorting POM. >> >> Regards, >> -- >> Christian >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');> >> For additional commands, e-mail: [email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');> >> >> > -- Sent from my phone
