Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5A705200B8C for ; Mon, 12 Sep 2016 11:11:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 58D28160AC8; Mon, 12 Sep 2016 09:11:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 02A80160AB8 for ; Mon, 12 Sep 2016 11:11:06 +0200 (CEST) Received: (qmail 20157 invoked by uid 500); 12 Sep 2016 09:11:05 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 20141 invoked by uid 99); 12 Sep 2016 09:11:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Sep 2016 09:11:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 85ABCC059C for ; Mon, 12 Sep 2016 09:11:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id PiBhSUFCPu3G for ; Mon, 12 Sep 2016 09:10:54 +0000 (UTC) Received: from mail-lf0-f43.google.com (mail-lf0-f43.google.com [209.85.215.43]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 219B35FAE3 for ; Mon, 12 Sep 2016 09:10:54 +0000 (UTC) Received: by mail-lf0-f43.google.com with SMTP id u14so82524415lfd.1 for ; Mon, 12 Sep 2016 02:10:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=5JajsWgl4qmimfuAtsvm/FhTdR2F7KEOozFTXjiyESw=; b=unAYvfngQPwQIDArHqMfZk1igpstKRlgCnPLDHFDoeg8wf8WseMC+jVVZuWDHUWdX5 WIonIiH0HBcXnFaW2wXhlxG8RU5v9814xqBpgzxGDShxSbd10SiNnZGUSmIr6lu/1esn 8qXL1hSfhrHS/6z2sy2VtLUJggQk1kug9LHPa5GHBW03vp7tj9Sgst7zkpSZKJnCS4Hi fyx9rAw7AjNEoTen1JWl0inicgUOcxzwRZM8DsRe7v8LiH6fSvdtdISYhCtZXbn9q4cz SqR5LOL+HCaOQ6IA+bzSWbduCtLqMIyC/BLfgDJlFIA+/8p6wIW1zCJrFT10T2a0OCaJ BGdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=5JajsWgl4qmimfuAtsvm/FhTdR2F7KEOozFTXjiyESw=; b=aRGW5iHgYOTtcAUvFwEm4DO9jxSkfnAQvCu7BKRCSTUy/Zo/32vjXkQgZ+4LOtE3Zx n/qMt99TLZvstWhFIclBhQ/KQ0xd2pKhv1wUgSwSsLjU3x2ftsmV9auVXhYDNN987II/ vXTcMGIxGS8IHaIa4I23lpjRNwdf+oO56oZPg9bFrC4gF9H8+o4qUu8N0cT4tnYtPHGu rMn1VwGvUafIdfcg1va5hoZlv6ciaR40zxSIQJgVg3x4OZ7n8CdnMik4T0RRqrMYNIP6 SfCJdOOE2DsyiETENOq+7xEhRHI+SCQp0ivvT716nzbEmEB6wTFrZeox1KOmnZLUW8Jf 5u4Q== X-Gm-Message-State: AE9vXwO/+CQtrZyE98W9C5oW+OyZncSjUl0An9XKKsKhNDvAJ9y02QLRYNnG7OLVjj01Bg== X-Received: by 10.46.32.167 with SMTP id g39mr2821689lji.33.1473671446735; Mon, 12 Sep 2016 02:10:46 -0700 (PDT) Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com. [209.85.215.45]) by smtp.gmail.com with ESMTPSA id 68sm1538967ljf.6.2016.09.12.02.10.45 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Sep 2016 02:10:45 -0700 (PDT) Received: by mail-lf0-f45.google.com with SMTP id g62so82108450lfe.3 for ; Mon, 12 Sep 2016 02:10:45 -0700 (PDT) X-Received: by 10.25.161.76 with SMTP id k73mr5124011lfe.26.1473671445026; Mon, 12 Sep 2016 02:10:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.81.66 with HTTP; Mon, 12 Sep 2016 02:10:44 -0700 (PDT) In-Reply-To: <3F948EA6-B5C2-4866-A005-81284078B498@pronoia-solutions.com> References: <3EBCC076-B318-4E2F-B326-9D9CCE116E85@pronoia-solutions.com> <00F28014-7419-472F-BD54-28D6639D8ED7@integratix.net> <3F948EA6-B5C2-4866-A005-81284078B498@pronoia-solutions.com> From: Nicola Ferraro Date: Mon, 12 Sep 2016 11:10:44 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Getting ready for Apache Camel 2.18 Release To: dev@camel.apache.org Content-Type: multipart/alternative; boundary=001a11402f1aff3776053c4bde07 archived-at: Mon, 12 Sep 2016 09:11:08 -0000 --001a11402f1aff3776053c4bde07 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I've worked on the spring-boot starters and BOM topic and opened a PR recently. You can find a summary here [ https://issues.apache.org/jira/browse/CAMEL-10222] and this is latest PR: https://github.com/apache/camel/pull/1164. Basically, the aim is allowing users to add camel components to their application by just adding the corresponding "xx-starter" project to their POM. This can be useful also for initializer tools like https://start.spring.io/ and the likes, to create skeleton of applications that just work, without having to worry about wrong transitive dependencies= . Starter projects take care of, eg. excluding unwanted logging libraries and including eg. libraries that are provided in other contexts. The new BOM part is a semi-automated way to generate a BOM for the users that fixes incompatibilities between the camel-parent BOM and the spring-boot-dependencies BOM. They currently differ for the minor (and sometimes major) version of many libraries, including eg. Jetty, ActiveMQ, Hibernate Validator, Cassandra driver, etc. Both BOMs also include specific versions of common libraries like guava, guice and gson that take precedence over the transitive versions required by the starters, resulting in camel components not working correctly. The new BOM (partly generated) should be used in place of the two Camel+Spring-boot BOMs to avoid such issues. I understand that this is a major change, so I ask your feedback about the problem (do we want to have this feature to solve these problems for users?) and the solution. Thanks On Fri, Sep 9, 2016 at 6:08 PM, Quinn Stevenson wrote: > Thanks for taking a look at the PR Thomas - I really appreciate the > feedback. > > 1) The parent pom was wrong because I created this PR before the change > from 2.18-SNAPSHOT to 2.18.0-SNAPSHOT took place - it=E2=80=99s been out = there a > while > 2) My bad on the READMEmd - you can probably tell where I copied the > example from to get started :-). I=E2=80=99ll get working on that to cle= an it up > 3) I really struggled with this - what example to use. I thought a > little about replacing JMS with something else, but I wasn=E2=80=99t quit= e sure > what to use. It gets a little more complicated because of the two JVMs > (one for Karaf and one for the bootstrap code). Anyway, if you have a > =E2=80=9Cgood=E2=80=9D test route and what you=E2=80=99d like to see happ= en for testing, I=E2=80=99d really > like to see it and I=E2=80=99ll try and use that instead. > 4) I=E2=80=99m not sure where I came up with the name of the example - b= ut you=E2=80=99re > right - I=E2=80=99ll change it to example-camel-test-karaf > 5) I=E2=80=99ll get back in and figure out why the integration test is fa= iling now > - I was certain they were working at one time. Anyway, the unit tests pa= ss > - but they generate a bunch of scary messages in the log files. I didn= =E2=80=99t > see this stuff when I was using the class I derived CamelKarafTestSupport > from. If you have any ideas on how to clean those up, I=E2=80=99d really= like to > hear them. > > I=E2=80=99ve got one other bug to fix, then I=E2=80=99ll get back on this= one. > > If you wouldn=E2=80=99t mind =E2=80=9Cwatching=E2=80=9D the JIRA for this= ( > https://issues.apache.org/jira/browse/CAMEL-6132 < > https://issues.apache.org/jira/browse/CAMEL-6132>), we can communicate > there (rather than spam the DEV list). > > Thanks Again > > > > On Sep 8, 2016, at 11:09 AM, Walzer, Thomas < > thomas.walzer@integratix.net> wrote: > > > > Hi, Quinn, > > > > I took a look at PR987: > > > > 1) the parent pom should be something like 2.18.0 not 2.18 (maybe the P= R > was around too long, so the parent changed). > > 2) The readme really needs some love. It mentions spring when there is > really blueprint; jms, when there is none, etc. > > 3) for me an example replacing/redefining jms: or activemq: by seda: > would really make a difference. Like having a jms-definitions-bp.xml and > then replacing it by seda-definitions-bp.xml, or something like that. I > know that=C2=B4s not the point of your sample but the timer-example seems= a bit > basic. > > 4) maybe =E2=80=A6-test-karaf would be a better name? > > 5) my unit tests and itests do not run through. If they would I could > provide more fleshy feedback. > > > > If I can help, let me know. > > > > Cheers, Thomas. > > > > ------------------------------------------------------- > > T E S T S > > ------------------------------------------------------- > > Running org.apache.camel.BlueprintBeanPropertiesOverrideFromFileTest > > Unable to start bundle: org.apache.felix.gogo.runtime [64] > > org.osgi.framework.BundleException: Unable to start bundle > > at org.apache.felix.connect.PojoSRBundle.start( > PojoSRBundle.java:163) > > at org.apache.felix.connect.PojoSR.startBundles(PojoSR.java:304) > > at org.apache.felix.connect.PojoSR.(PojoSR.java:248) > > at org.apache.felix.connect.PojoSR.(PojoSR.java:129) > > at org.apache.felix.connect.PojoServiceRegistryFactoryImpl > .newPojoServiceRegistry(PojoServiceRegistryFactoryImpl.java:52) > > at org.apache.camel.test.blueprint.CamelBlueprintHelper. > createBundleContext(CamelBlueprintHelper.java:173) > > at org.apache.camel.test.blueprint.CamelBlueprintHelper. > createBundleContext(CamelBlueprintHelper.java:119) > > at org.apache.camel.test.blueprint.CamelBlueprintTestSupport. > createBundleContext(CamelBlueprintTestSupport.java:127) > > at org.apache.camel.test.blueprint.CamelBlueprintTestSupport. > setUp(CamelBlueprintTestSupport.java:241) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:62) > > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:483) > > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall( > FrameworkMethod.java:50) > > at org.junit.internal.runners.model.ReflectiveCallable.run( > ReflectiveCallable.java:12) > > at org.junit.runners.model.FrameworkMethod.invokeExplosively( > FrameworkMethod.java:47) > > at org.junit.internal.runners.statements.RunBefores. > evaluate(RunBefores.java:24) > > at org.junit.internal.runners.statements.RunAfters.evaluate( > RunAfters.java:27) > > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > > at org.junit.runners.BlockJUnit4ClassRunner.runChild( > BlockJUnit4ClassRunner.java:78) > > at org.junit.runners.BlockJUnit4ClassRunner.runChild( > BlockJUnit4ClassRunner.java:57) > > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71= ) > > at org.junit.runners.ParentRunner.runChildren( > ParentRunner.java:288) > > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58= ) > > at org.junit.runners.ParentRunner$2.evaluate( > ParentRunner.java:268) > > at org.junit.internal.runners.statements.RunAfters.evaluate( > RunAfters.java:27) > > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > > at org.apache.maven.surefire.junit4.JUnit4Provider.execute( > JUnit4Provider.java:367) > > at org.apache.maven.surefire.junit4.JUnit4Provider. > executeWithRerun(JUnit4Provider.java:274) > > at org.apache.maven.surefire.junit4.JUnit4Provider. > executeTestSet(JUnit4Provider.java:238) > > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke( > JUnit4Provider.java:161) > > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > Caused by: java.lang.IllegalStateException: Thread Print Stream already > set > > at org.apache.felix.gogo.runtime.threadio.ThreadIOImpl.start( > ThreadIOImpl.java:49) > > at org.apache.felix.gogo.runtime.activator.Activator.start( > Activator.java:76) > > at org.apache.felix.connect.PojoSRBundle.start( > PojoSRBundle.java:153) > > ... 37 more > > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.485 > sec - in org.apache.camel.BlueprintBeanPropertiesOverrideFromFileTest > > Running org.apache.camel.BlueprintBeanPropertiesOverrideFromTestTest > > Unable to start bundle: org.apache.felix.gogo.runtime [64] > > org.osgi.framework.BundleException: Unable to start bundle > > at org.apache.felix.connect.PojoSRBundle.start( > PojoSRBundle.java:163) > > at org.apache.felix.connect.PojoSR.startBundles(PojoSR.java:304) > > at org.apache.felix.connect.PojoSR.(PojoSR.java:248) > > at org.apache.felix.connect.PojoSR.(PojoSR.java:129) > > at org.apache.felix.connect.PojoServiceRegistryFactoryImpl > .newPojoServiceRegistry(PojoServiceRegistryFactoryImpl.java:52) > > at org.apache.camel.test.blueprint.CamelBlueprintHelper. > createBundleContext(CamelBlueprintHelper.java:173) > > at org.apache.camel.test.blueprint.CamelBlueprintHelper. > createBundleContext(CamelBlueprintHelper.java:119) > > at org.apache.camel.test.blueprint.CamelBlueprintTestSupport. > createBundleContext(CamelBlueprintTestSupport.java:127) > > at org.apache.camel.test.blueprint.CamelBlueprintTestSupport. > setUp(CamelBlueprintTestSupport.java:241) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:62) > > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:483) > > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall( > FrameworkMethod.java:50) > > at org.junit.internal.runners.model.ReflectiveCallable.run( > ReflectiveCallable.java:12) > > at org.junit.runners.model.FrameworkMethod.invokeExplosively( > FrameworkMethod.java:47) > > at org.junit.internal.runners.statements.RunBefores. > evaluate(RunBefores.java:24) > > at org.junit.internal.runners.statements.RunAfters.evaluate( > RunAfters.java:27) > > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > > at org.junit.runners.BlockJUnit4ClassRunner.runChild( > BlockJUnit4ClassRunner.java:78) > > at org.junit.runners.BlockJUnit4ClassRunner.runChild( > BlockJUnit4ClassRunner.java:57) > > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71= ) > > at org.junit.runners.ParentRunner.runChildren( > ParentRunner.java:288) > > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58= ) > > at org.junit.runners.ParentRunner$2.evaluate( > ParentRunner.java:268) > > at org.junit.internal.runners.statements.RunAfters.evaluate( > RunAfters.java:27) > > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > > at org.apache.maven.surefire.junit4.JUnit4Provider.execute( > JUnit4Provider.java:367) > > at org.apache.maven.surefire.junit4.JUnit4Provider. > executeWithRerun(JUnit4Provider.java:274) > > at org.apache.maven.surefire.junit4.JUnit4Provider. > executeTestSet(JUnit4Provider.java:238) > > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke( > JUnit4Provider.java:161) > > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > Caused by: java.lang.IllegalStateException: Thread Print Stream already > set > > at org.apache.felix.gogo.runtime.threadio.ThreadIOImpl.start( > ThreadIOImpl.java:49) > > at org.apache.felix.gogo.runtime.activator.Activator.start( > Activator.java:76) > > at org.apache.felix.connect.PojoSRBundle.start( > PojoSRBundle.java:153) > > ... 37 more > > *ERROR* Cannot use configuration HelloBean for [org.osgi.service.cm.Man= agedService, > id=3D63, bundle=3D1/jar:file:/Users/thomas/camel/examples/camel- > example-blueprint/target/test-bundles/blueprintbeanpropertiesoverrid > efromtesttest-1473353703335.jar!/]: No visibility to configuration bound > to file:/Users/thomas/camel/examples/camel-example- > blueprint/target/classes/ > > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 38.07 > sec - in org.apache.camel.BlueprintBeanPropertiesOverrideFromTestTest > > Running org.apache.camel.BlueprintBeanTest > > Unable to start bundle: org.apache.felix.gogo.runtime [64] > > org.osgi.framework.BundleException: Unable to start bundle > > at org.apache.felix.connect.PojoSRBundle.start( > PojoSRBundle.java:163) > > at org.apache.felix.connect.PojoSR.startBundles(PojoSR.java:304) > > at org.apache.felix.connect.PojoSR.(PojoSR.java:248) > > at org.apache.felix.connect.PojoSR.(PojoSR.java:129) > > at org.apache.felix.connect.PojoServiceRegistryFactoryImpl > .newPojoServiceRegistry(PojoServiceRegistryFactoryImpl.java:52) > > at org.apache.camel.test.blueprint.CamelBlueprintHelper. > createBundleContext(CamelBlueprintHelper.java:173) > > at org.apache.camel.test.blueprint.CamelBlueprintHelper. > createBundleContext(CamelBlueprintHelper.java:119) > > at org.apache.camel.test.blueprint.CamelBlueprintTestSupport. > createBundleContext(CamelBlueprintTestSupport.java:127) > > at org.apache.camel.test.blueprint.CamelBlueprintTestSupport. > setUp(CamelBlueprintTestSupport.java:237) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:62) > > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:483) > > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall( > FrameworkMethod.java:50) > > at org.junit.internal.runners.model.ReflectiveCallable.run( > ReflectiveCallable.java:12) > > at org.junit.runners.model.FrameworkMethod.invokeExplosively( > FrameworkMethod.java:47) > > at org.junit.internal.runners.statements.RunBefores. > evaluate(RunBefores.java:24) > > at org.junit.internal.runners.statements.RunAfters.evaluate( > RunAfters.java:27) > > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > > at org.junit.runners.BlockJUnit4ClassRunner.runChild( > BlockJUnit4ClassRunner.java:78) > > at org.junit.runners.BlockJUnit4ClassRunner.runChild( > BlockJUnit4ClassRunner.java:57) > > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71= ) > > at org.junit.runners.ParentRunner.runChildren( > ParentRunner.java:288) > > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58= ) > > at org.junit.runners.ParentRunner$2.evaluate( > ParentRunner.java:268) > > at org.junit.internal.runners.statements.RunAfters.evaluate( > RunAfters.java:27) > > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > > at org.apache.maven.surefire.junit4.JUnit4Provider.execute( > JUnit4Provider.java:367) > > at org.apache.maven.surefire.junit4.JUnit4Provider. > executeWithRerun(JUnit4Provider.java:274) > > at org.apache.maven.surefire.junit4.JUnit4Provider. > executeTestSet(JUnit4Provider.java:238) > > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke( > JUnit4Provider.java:161) > > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:290) > > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:242) > > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:121) > > Caused by: java.lang.IllegalStateException: Thread Print Stream already > set > > at org.apache.felix.gogo.runtime.threadio.ThreadIOImpl.start( > ThreadIOImpl.java:49) > > at org.apache.felix.gogo.runtime.activator.Activator.start( > Activator.java:76) > > at org.apache.felix.connect.PojoSRBundle.start( > PojoSRBundle.java:153) > > ... 37 more > > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.425 > sec - in org.apache.camel.BlueprintBeanTest > > > > Results : > > > > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0 > > > > [INFO] > > [INFO] --- maven-bundle-plugin:3.2.0:manifest (bundle-manifest) @ > camel-example-blueprint --- > > [WARNING] Manifest org.apache.camel:camel-example-blueprint:bundle:2.18= .0-SNAPSHOT > : Unused Import-Package instructions: [org.apache.camel.*, > org.springframework.ws.*, org.springframework.xml.*, org.springframework.= *, > org.apache.commons.logging.*, org.apache.cxf.*, org.apache.qpid.*, > org.apache.abdera.*, org.apache.commons.httpclient.*, > org.apache.velocity.*, org.apache.xmlbeans.*, org.eclipse.jetty.*, > com.thoughtworks.xstream.*, org.antlr.stringtemplate.*, > org.ccil.cowan.tagsoup.*, org.mortbay.cometd.*, org.slf4j.*, > net.sf.flatpack.*, net.sf.saxon.*, freemarker.*, javax.persistence.*, > org.apache.lucene.*, org.apache.solr.*] > > [INFO] > > [INFO] --- maven-bundle-plugin:3.2.0:bundle (default-bundle) @ > camel-example-blueprint --- > > [WARNING] Bundle org.apache.camel:camel-example-blueprint:bundle:2.18.0= -SNAPSHOT > : No translation found for macro: greeting > > [WARNING] Bundle org.apache.camel:camel-example-blueprint:bundle:2.18.0= -SNAPSHOT > : No translation found for macro: body > > [WARNING] Bundle org.apache.camel:camel-example-blueprint:bundle:2.18.0= -SNAPSHOT > : Unused Import-Package instructions: [org.springframework.ws.*, > org.springframework.xml.*, org.springframework.*, > org.apache.commons.logging.*, org.apache.cxf.*, org.apache.qpid.*, > org.apache.abdera.*, org.apache.commons.httpclient.*, > org.apache.velocity.*, org.apache.xmlbeans.*, org.eclipse.jetty.*, > com.thoughtworks.xstream.*, org.antlr.stringtemplate.*, > org.ccil.cowan.tagsoup.*, org.mortbay.cometd.*, org.slf4j.*, > net.sf.flatpack.*, net.sf.saxon.*, freemarker.*, javax.persistence.*, > org.apache.lucene.*, org.apache.solr.*] > > [INFO] > > [INFO] --- maven-site-plugin:3.5.1:attach-descriptor > (attach-descriptor) @ camel-example-blueprint --- > > [INFO] > > [INFO] --- maven-failsafe-plugin:2.19.1:integration-test (default) @ > camel-example-blueprint --- > > > > ------------------------------------------------------- > > T E S T S > > ------------------------------------------------------- > > Running org.apache.camel.itest.BlueprintBeanIT > > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.392 > sec <<< FAILURE! - in org.apache.camel.itest.BlueprintBeanIT > > initializationError(org.apache.camel.itest.BlueprintBeanIT) Time > elapsed: 0.01 sec <<< ERROR! > > org.ops4j.pax.exam.TestContainerException: java.lang.reflect. > InvocationTargetException > > at org.apache.camel.itest.BlueprintBeanIT.configure( > BlueprintBeanIT.java:60) > > > > Running org.apache.camel.itest.BlueprintBeanPropertiesOverrideFromFileI= T > > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.029 > sec <<< FAILURE! - in org.apache.camel.itest. > BlueprintBeanPropertiesOverrideFromFileIT > > initializationError(org.apache.camel.itest. > BlueprintBeanPropertiesOverrideFromFileIT) Time elapsed: 0.001 sec <<< > ERROR! > > org.ops4j.pax.exam.TestContainerException: java.lang.reflect. > InvocationTargetException > > at org.apache.camel.itest.BlueprintBeanPropertiesOverrid > eFromFileIT.configure(BlueprintBeanPropertiesOverrideFromFileIT.java:76) > > > > Running org.apache.camel.itest.BlueprintBeanPropertiesOverrideFromTestI= T > > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.015 > sec <<< FAILURE! - in org.apache.camel.itest. > BlueprintBeanPropertiesOverrideFromTestIT > > initializationError(org.apache.camel.itest. > BlueprintBeanPropertiesOverrideFromTestIT) Time elapsed: 0.001 sec <<< > ERROR! > > org.ops4j.pax.exam.TestContainerException: java.lang.reflect. > InvocationTargetException > > at org.apache.camel.itest.BlueprintBeanPropertiesOverrid > eFromTestIT.configure(BlueprintBeanPropertiesOverrideFromTestIT.java:90) > > > > > > Results : > > > > Tests in error: > > BlueprintBeanIT.initializationError =C2=BB TestContainer > java.lang.reflect.Invocati... > > BlueprintBeanPropertiesOverrideFromFileIT.initializationError =C2=BB > TestContainer ... > > BlueprintBeanPropertiesOverrideFromTestIT.initializationError =C2=BB > TestContainer ... > > > > Tests run: 3, Failures: 0, Errors: 3, Skipped: 0 > > > > [INFO] > > [INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) > @ camel-example-blueprint --- > > [INFO] Checking legal files in: camel-example-blueprint-2.18. > 0-SNAPSHOT.jar > > [INFO] > > [INFO] --- maven-failsafe-plugin:2.19.1:verify (default) @ > camel-example-blueprint --- > > [INFO] ------------------------------------------------------------ > ------------ > > [INFO] BUILD FAILURE > > [INFO] ------------------------------------------------------------ > ------------ > > > > > >> Am 02.09.2016 um 17:12 schrieb Quinn Stevenson < > quinn@pronoia-solutions.com>: > >> > >> I=E2=80=99ve had a pull-request out there for a while ( > https://github.com/apache/camel/pull/987 camel/pull/987>) - looking for some feedback on the example project that > attempts to show how to use camel-test-karaf. I could really use some > input. I think fleshing-out this example will help refine the > camel-test-karaf component itself. > >> > >> > >>> On Aug 30, 2016, at 4:17 AM, Luca Burgazzoli > wrote: > >>> > >>> Hi Claus, > >>> > >>> Yep, I'm going to close CAMEL-10274. > >>> > >>> --- > >>> Luca Burgazzoli > >>> > >>> > >>> On Tue, Aug 30, 2016 at 11:25 AM, Claus Ibsen > wrote: > >>>> Hi Luca > >>>> > >>>> I can see you found out about the problem and found a solution. So t= he > >>>> examples should work again. > >>>> > >>>> On Mon, Aug 29, 2016 at 12:39 PM, Luca Burgazzoli < > lburgazzoli@gmail.com> wrote: > >>>>> Hi Claus, > >>>>> > >>>>> can you tell me something more about log4j2 vs jetty plugin ? > >>>>> > >>>>> --- > >>>>> Luca Burgazzoli > >>>>> > >>>>> > >>>>> On Sun, Aug 28, 2016 at 11:28 AM, Claus Ibsen > wrote: > >>>>>> Hi > >>>>>> > >>>>>> Hope everybody had good summer vacation. I had my vacation in part= s > >>>>>> and have next week as PTO. > >>>>>> > >>>>>> We should get started to close down on the upcoming Camel 2.18 > release. > >>>>>> > >>>>>> > >>>>>> There is some outstanding work (in no particular order) > >>>>>> > >>>>>> 1) > >>>>>> Finish the spring boot stuff with the starter components. > >>>>>> Nicola comes back from PTO and will work on this. > >>>>>> > >>>>>> 2) > >>>>>> rest-dsl to support calling REST services. I am working on this an= d > >>>>>> have some outstanding work still around binding and other > >>>>>> improvements. > >>>>>> > >>>>>> 3) > >>>>>> Tidy up the log4j v2 upgrade. Some of the examples do not start wi= th > >>>>>> the jetty plugin. > >>>>>> > >>>>>> 4) > >>>>>> Migrate the last wiki pages to adoc files. There is not so many > pages > >>>>>> left and you can find a report when running camel-catalog build th= at > >>>>>> output what is missing. > >>>>>> > >>>>>> This will help us with a base-line for maintaining the documentati= on > >>>>>> going forward in the source code adoc files instead of wiki, and w= e > >>>>>> can then generate a new website and documentation for the followin= g > >>>>>> release (2.19 or 3.0) etc. But this is a discussion we should IMHO > >>>>>> take post 2.18. > >>>>>> > >>>>>> 5) > >>>>>> camel-test-karaf module. This module is in the works but could use > >>>>>> some review and finishing so its easier to use for end users. > >>>>>> > >>>>>> Notice the existing camel-test-blueprint is still favored for doin= g > >>>>>> unit tests which you can run fast and easily debug. The new > >>>>>> camel-test-karaf is for running integration tests in a running kar= af > >>>>>> instance. > >>>>>> > >>>>>> 6) > >>>>>> We should look at the JIRA tickets that are assigned to 2.18.0 and > try > >>>>>> to fix / implement them, or move them to 2.18.1 or 2.19.0 for next > >>>>>> releases. > >>>>>> > >>>>>> 7) > >>>>>> Keep an eye on the CI server to make sure the tests are green. > >>>>>> https://builds.apache.org/view/A-D/view/Camel/ > >>>>>> > >>>>>> > >>>>>> If all goes well then hopefully in 2-3 weeks we are ready to cut > the 2.18.0 RC. > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Claus Ibsen > >>>>>> ----------------- > >>>>>> http://davsclaus.com @davsclaus > >>>>>> Camel in Action 2: https://www.manning.com/ibsen2 > >>>> > >>>> > >>>> > >>>> -- > >>>> Claus Ibsen > >>>> ----------------- > >>>> http://davsclaus.com @davsclaus > >>>> Camel in Action 2: https://www.manning.com/ibsen2 > >> > > > > --001a11402f1aff3776053c4bde07--