Hi,
I would advice to keep Camel BOM imported and import also Spring BOM. Keep
in mind that the order is important here - Spring BOM first, Camel BOM
second. This is actually pretty common approach - to import Spring and
Camel BOMs at the same time. Works like a charm - I'm using this approach
myself. :)
In particular this approach is recommended when working with
camel-spring-boot. The end user should choose his/her Spring stack version
of choice and then just add Camel to the mix.
Cheers!
czw., 21.05.2015 o 16:51 użytkownik Ronny Aerts <ronny.ae...@intris.be>
napisał:
> Hello,
>
> This works very fine for everything which has to do with camel (as
> groupid) itself but not for dependencies with other groupid like the one
> below:
> <dependencies>
> <dependency>
> <groupId>org.springframework.ws</groupId>
> <artifactId>spring-ws-security</artifactId>
> <version>${spring-ws-version}</version>
> </dependency>
> </dependencies>
> --
> vriendelijke groeten,
> Ronny Aerts – Intris nv – Wapenstilstandlaan 47, 2600 Berchem, België
> R&D Integration Architect
> Prince II certified – ITIL certified
> Tel: +32-3-326.50.75
>
> -----Original Message-----
> From: Henryk Konsek [mailto:hekon...@gmail.com]
> Sent: vrijdag 15 mei 2015 17:23
> To: users@camel.apache.org
> Subject: Re: camel-parent pom properties
>
> Hi,
>
> The better practice is to import Camel parent as BOM:
>
>
> <dependencyManagement>
> <dependnecies>
> <dependency>
> <groupId>org.apache.camel</groupId>
> <artifactId>camel-parent</artifactId>
> <version>${camel.version}</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> </dependnecies>
> </dependencyManagement>
>
> And then simply:
>
> <dependency>
> <groupId>org.apache.camel</groupId>
> <artifactId>camel-core</artifactId>
> </dependency>
>
> Cheers!
>
> pt., 15.05.2015 o 15:24 użytkownik Ronny Aerts <ronny.ae...@intris.be>
> napisał:
>
> Hello camel community,
>
> I'm interested in using the maven properties which are defined in the
> camel-parent pom.xml. In order to inherit these maven properties, I need to
> set the parent in my projects to the camel-parent. The point is that my
> projects use other version numbers than those of camel and this results in
> unresolvable camel-core references because the camel-parent uses the
> ${project.version} variable in its dependencies (which is not 2.15.2 in my
> projects).
>
> <dependency>
> <groupId>org.apache.camel</groupId>
> <artifactId>camel-core</artifactId>
> <version>${project.version}</version>
> </dependency>
>
> Is there a workaround for this?
>
> --
> vriendelijke groeten,
> Ronny Aerts<mailto:ronny.ae...@intris.be> - Intris nv -
> Wapenstilstandlaan 47, 2600 Berchem, België R&D Integration Architect
> Prince II<http://nl.wikipedia.org/wiki/PRINCE2> certified - ITIL<
> http://nl.wikipedia.org/wiki/Information_Technology_Infrastructure_Library
> >
> certified
> Tel: +32-3-326.50.75
>
> Intris nv
> Wapenstilstandlaan 47
> B-2600 Berchem Tel. +32 3 326 50 75
> Fax +32 3 326 42 23
> www.intris.be<http://www.intris.be/> [
> http://www.intris.be/mail/AEO_Sticker_108pxRGB.jpg] <http://www.intris.be>
>
> DISCLAIMER
> This is an e-mail from Intris. The information contained in this
> communication is intended solely for use by the individual or entity to
> whom it is addressed.
> Use of this communication by others is prohibited. If the e-mail message
> was sent to you by mistake, please notify supp...@intris.be<mailto:
> supp...@intris.be>, destroy it without reading, using, copying or
> disclosing its contents to any other person.
> We accept no liability for damage related to data and/or documents which
> are communicated by electronic mail.
> Intris nv
> Wapenstilstandlaan 47
> B-2600 Berchem Tel. +32 3 326 50 75
> Fax +32 3 326 42 23
> www.intris.be<http://www.intris.be/> [
> http://www.intris.be/mail/AEO_Sticker_108pxRGB.jpg] <http://www.intris.be>
>
> DISCLAIMER
> This is an e-mail from Intris. The information contained in this
> communication is intended solely for use by the individual or entity to
> whom it is addressed.
> Use of this communication by others is prohibited. If the e-mail message
> was sent to you by mistake, please notify supp...@intris.be<mailto:
> supp...@intris.be>, destroy it without reading, using, copying or
> disclosing its contents to any other person.
> We accept no liability for damage related to data and/or documents which
> are communicated by electronic mail.
>
