[jira] [Updated] (CAMEL-9142) dropped support for multiple blueprint descriptors in unit tests
[ https://issues.apache.org/jira/browse/CAMEL-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-9142: --- Fix Version/s: 2.15.4 2.16.0 > dropped support for multiple blueprint descriptors in unit tests > > > Key: CAMEL-9142 > URL: https://issues.apache.org/jira/browse/CAMEL-9142 > Project: Camel > Issue Type: Bug > Components: camel-test >Affects Versions: 2.15.3 >Reporter: Scott Cranton >Priority: Minor > Fix For: 2.16.0, 2.15.4 > > > Looks like update CAMEL-8948 dropped support for multiple blueprint > descriptors within CamelBlueprintTestSupport file within camel-test-blueprint > component. The symptom is a 'java.lang.RuntimeException: InputStream cannot > be null' for unit tests that have a getBlueprintDescriptor with multiple file > references, i.e. a '+' concatenating two or more descriptor files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-9142) dropped support for multiple blueprint descriptors in unit tests
[ https://issues.apache.org/jira/browse/CAMEL-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-9142: --- Component/s: camel-test > dropped support for multiple blueprint descriptors in unit tests > > > Key: CAMEL-9142 > URL: https://issues.apache.org/jira/browse/CAMEL-9142 > Project: Camel > Issue Type: Bug > Components: camel-test >Affects Versions: 2.15.3 >Reporter: Scott Cranton >Priority: Minor > Fix For: 2.16.0, 2.15.4 > > > Looks like update CAMEL-8948 dropped support for multiple blueprint > descriptors within CamelBlueprintTestSupport file within camel-test-blueprint > component. The symptom is a 'java.lang.RuntimeException: InputStream cannot > be null' for unit tests that have a getBlueprintDescriptor with multiple file > references, i.e. a '+' concatenating two or more descriptor files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-9142) dropped support for multiple blueprint descriptors in unit tests
[ https://issues.apache.org/jira/browse/CAMEL-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cranton updated CAMEL-9142: - Description: Looks like update CAMEL-8948 dropped support for multiple blueprint descriptors within CamelBlueprintTestSupport file within camel-test-blueprint component. The symptom is a 'java.lang.RuntimeException: InputStream cannot be null' for unit tests that have a getBlueprintDescriptor with multiple file references, i.e. a '+' concatenating two or more descriptor files. (was: Looks like update CAMEL-8948 dropped support for multiple blueprint descriptors within CamelBlueprintTestSupport file within camel-test-blueprint component. The symptom is a null input stream for unit tests that have a getBlueprintDescriptor with multiple file references, i.e. a '+' concatenating two or more descriptor files.) > dropped support for multiple blueprint descriptors in unit tests > > > Key: CAMEL-9142 > URL: https://issues.apache.org/jira/browse/CAMEL-9142 > Project: Camel > Issue Type: Bug >Affects Versions: 2.15.3 >Reporter: Scott Cranton >Priority: Minor > > Looks like update CAMEL-8948 dropped support for multiple blueprint > descriptors within CamelBlueprintTestSupport file within camel-test-blueprint > component. The symptom is a 'java.lang.RuntimeException: InputStream cannot > be null' for unit tests that have a getBlueprintDescriptor with multiple file > references, i.e. a '+' concatenating two or more descriptor files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-9142) dropped support for multiple blueprint descriptors in unit tests
[ https://issues.apache.org/jira/browse/CAMEL-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cranton updated CAMEL-9142: - Description: Looks like update CAMEL-8948 dropped support for multiple blueprint descriptors within CamelBlueprintTestSupport file within camel-test-blueprint component. The symptom is a null input stream for unit tests that have a getBlueprintDescriptor with multiple file references, i.e. a '+' concatenating two or more descriptor files. > dropped support for multiple blueprint descriptors in unit tests > > > Key: CAMEL-9142 > URL: https://issues.apache.org/jira/browse/CAMEL-9142 > Project: Camel > Issue Type: Bug >Affects Versions: 2.15.3 >Reporter: Scott Cranton >Priority: Minor > > Looks like update CAMEL-8948 dropped support for multiple blueprint > descriptors within CamelBlueprintTestSupport file within camel-test-blueprint > component. The symptom is a null input stream for unit tests that have a > getBlueprintDescriptor with multiple file references, i.e. a '+' > concatenating two or more descriptor files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-9142) dropped support for multiple blueprint descriptors in unit tests
[ https://issues.apache.org/jira/browse/CAMEL-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cranton updated CAMEL-9142: - Patch Info: Patch Available > dropped support for multiple blueprint descriptors in unit tests > > > Key: CAMEL-9142 > URL: https://issues.apache.org/jira/browse/CAMEL-9142 > Project: Camel > Issue Type: Bug >Affects Versions: 2.15.3 >Reporter: Scott Cranton >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
