>>>>> Steinar Bang <[email protected]>:
> For one of my projects I ended up restructuring the entire project,
> moving the current top pom down one level and create a new top level
> with two maven modules: a BOM and the project proper
> https://github.com/steinarb/authservice :
> authservice/
> authservice/pom.xml
> authservice/authservice-bom/
> authservice/authservice-bom/pom.xml
> authservice/authservice/
> authservice/authservice/pom.xml
> The reason for this reorganization was to keep versions set by
> imported BOMs from leaking out into the BOM my project provides.
Note: I'm not sayin that the karaf BOM was to blame for this.
I'm just saying that doing something like
<dependencyManagement>
<dependencies>
<dependency>
<groupId>no.priv.bang.beans</groupId>
<artifactId>beans-bom</artifactId>
<version>${beans.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
into the effective POM of a BOM causes the dependencies of beans-bom (in
he example) to be included everywhere that BOM is imported.
