[
https://issues.apache.org/jira/browse/CAMEL-10293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470046#comment-15470046
]
Marcin Domanski commented on CAMEL-10293:
-----------------------------------------
Well, long story short, we are converting some projects from Spring DSL to
Blueprint.
Colleague of mine was running different test on the SNAPSHOT and just noted
that camel:run stopped working when any (even empty) blueprint file was in
place (it did not work because there was a conflict between activemq 5.6
dependencies and lastest maven plugin 2.17.3 - both are importing OSGi
dependencies, but that is a different story).
I know you usually don't maintain both spring DSL and Blueprint in one project,
but here: http://camel.apache.org/camel-maven-plugin.html it is stated
following (while describing fileApplicationContextUri tag): "It can also be
used to replace configuration that requires an OSGi container with an
equivalent non-OSGi configuration."
> [camel-maven-plugin] When blueprint detected, plugin ignores useBlueprint,
> fileApplicationContextUri tags
> ---------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-10293
> URL: https://issues.apache.org/jira/browse/CAMEL-10293
> Project: Camel
> Issue Type: Bug
> Components: build system, tests
> Affects Versions: 2.17.3
> Reporter: Marcin Domanski
> Priority: Minor
>
> It seems not to be possible to force camel:run to use Spring DSL file if OSGi
> bluepring is available. Following configuration is completely ignored if
> there is a blueprint in OSGI-INF folder:
> {code:xml}
> <plugin>
> <groupId>org.apache.camel</groupId>
> <artifactId>camel-maven-plugin</artifactId>
> <version>2.17.3</version>
> <configuration>
> <useBlueprint>false</useBlueprint>
> <fileApplicationContextUri>
> META-INF/spring/camel-context.xml
> </fileApplicationContextUri>
> </configuration>
> </plugin>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
