There are 2 different options, both of which aren't ideal IMO:
1) use the IP-BOM as a BOM in our BOMs - that would mean that *all the dependencies from the IP-BOM* would be visible to clients, which is not good. If they wanted that, clients could just use the IP-BOM directly.
2) use the IP-BOM as a parent (Maven-wise) in our BOMs. That's not ideal because there are still some dependencies which are not present in the IP-BOM - the most notable are the `eclipse.*` ones, meaning we'd have 2 places to maintain dependencies