On 25/09/2023 23.14, Steven Huypens wrote:
Hi Robert,
Hello Stephen,
Seems like a fair point to me, I agree the Karaf BOM should only list Karaf dependencies. It would be nice though to be able to 'use' the library versions Karaf is using for third party dependencies, without having to import karaf.git/pom.xml. Any ideas for that? Please keep in mind that starting from Maven 4.0, a new specific BOM packaging <https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#bill-of-materials-bom-poms> has been introduced. I have not looked into it, but it might be worth looking at before making any changes.
Thanks for the pointer. That piece of maven documentation seems to have vastly improved since I last read everything there was on "scope=import" :)
As I understand, the forward compatibility warning is regarding the layout and relaxes the "BOM must be a parent" model outlined in the documentation. The interplay goes toward https://www.youtube.com/watch?v=KDAmlNKZJto (the best I could find off the top my head) and there was some implication with the new POM XSD -- I saw a presentation somewhere, where a lot of ceremony was removed from a multi-module pom.xml, but I don't have that handy.
Regards, Robert
OpenPGP_signature
Description: OpenPGP digital signature
