Hi Claus-
Question: I’m planning to update some BOMs for other projects and was wondering
if there were other reasons to use a hard-coded value vs a property? I agree,
using ${project.version} is not going to work for a bom.
Would using a declared property such as ${apache.camel.version} have any
unintended side-effects?
Thanks,
Matt Pavlovich
> On Mar 10, 2024, at 7:34 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:
>
> Hi
>
> https://issues.apache.org/jira/browse/CAMEL-20413
>
> The BOM we release for both core and SB have
>
> <dependency>
> <groupId>org.apache.camel</groupId>
> <artifactId>camel-api</artifactId>
> <version>${project.version}</version>
> </dependency>
>
> But they should use the hardcoded release version, eg:
>
> <dependency>
> <groupId>org.apache.camel</groupId>
> <artifactId>camel-api</artifactId>
> <version>4.4.0</version>
> </dependency>
>
> If you look what we do now its wrong
> https://repo1.maven.org/maven2/org/apache/camel/camel-bom/4.4.0/camel-bom-4.4.0.pom
>
> This PR fixes camel-bom
> https://github.com/apache/camel/pull/13432
>
> Then we also need a fix for camel-spring-boot BOM as well
>
>
>
>
>
> --
> Claus Ibsen
> -----------------
> @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
