You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/04/06 08:45:16 UTC

[jira] [Resolved] (CAMEL-6244) camel:run in blueprint is broken

     [ https://issues.apache.org/jira/browse/CAMEL-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-6244.
--------------------------------

    Resolution: Fixed

All deps on camel-blueprint for blueprint stuff should be provided scope so they wont conflict when running with camel:run or testing. 

Also made sure camel:run dont have duplicate jars in the classpath by using a set / and made the classpath logging per line so its easier to read.
                
> camel:run in blueprint is broken
> --------------------------------
>
>                 Key: CAMEL-6244
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6244
>             Project: Camel
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 2.11.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.11.0
>
>
> Due the Aries blueprint upgrade then the blueprint extenders may run 2+ due classpath issues.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira