Camel.2.17.x.notest - Build # 127 - Fixed

[Apache Jenkins Server]

The Apache Jenkins build system has built Camel.2.17.x.notest (build #127)

Status: Fixed

Check console output at https://builds.apache.org/job/Camel.2.17.x.notest/127/ 
to view the results.

[GitHub] camel pull request #1172: CAMEL-10303 - added ability to detect when the con...

[hqstevenson]

GitHub user hqstevenson opened a pull request:

https://github.com/apache/camel/pull/1172

CAMEL-10303 - added ability to detect when the consumer fails to deli…

…ver the MLLP acknowledgement

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/hqstevenson/camel CAMEL-10303

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1172.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1172


commit c6336e8d09620b236de54c4138565eccd5cb4faa
Author: Quinn Stevenson 
Date:   2016-09-12T18:47:10Z

CAMEL-10303 - added ability to detect when the consumer fails to deliver 
the MLLP acknowledgement




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1171: camel-telegram: small improvements

[nicolaferraro]

Github user nicolaferraro closed the pull request at:

https://github.com/apache/camel/pull/1171


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1170: [CAMEL-10311] Comprehensively define lucene artefa...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/camel/pull/1170


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1171: camel-telegram: small improvements

[nicolaferraro]

GitHub user nicolaferraro opened a pull request:

https://github.com/apache/camel/pull/1171

camel-telegram: small improvements

- Added fallback converter for generic types. 
- Added configuration at component level.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nicolaferraro/camel TELEGRAM-SB

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1171.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1171


commit 725635f6f305518fbd1e6a33903ea5c1371df170
Author: Nicola Ferraro 
Date:   2016-09-09T16:35:55Z

camel-telegram: adding fallback converter for any object

commit 38b3e8bcb33bef80e4a8d92180fceca72e8cb342
Author: Nicola Ferraro 
Date:   2016-09-12T10:45:06Z

camel-telegram: adding default token configuration




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: camel git commit: Upgraded ES and aligned lucene/solr to match

[Andrea Cosentino]

We have to remember to use the new 2.3.5 ES bundle when it will be available.
 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Monday, September 12, 2016 12:16 PM, "davscl...@apache.org" 
 wrote:
Repository: camel
Updated Branches:
  refs/heads/master d6e32cde6 -> d09389eb4


Upgraded ES and aligned lucene/solr to match


Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/d09389eb
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/d09389eb
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/d09389eb

Branch: refs/heads/master
Commit: d09389eb476a38202e5a3c0a91d6f825d76da297
Parents: d6e32cd
Author: Claus Ibsen 
Authored: Mon Sep 12 12:15:57 2016 +0200
Committer: Claus Ibsen 
Committed: Mon Sep 12 12:15:57 2016 +0200

--
parent/pom.xml | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/camel/blob/d09389eb/parent/pom.xml
--
diff --git a/parent/pom.xml b/parent/pom.xml
index 08500c3..b2e7b83 100644
--- a/parent/pom.xml
+++ b/parent/pom.xml
@@ -169,7 +169,7 @@
 4.6.1
 2.3.1_1
 18.0
-2.3.1
+2.3.5
 
2.3.0.0
 1.2
 1.0.1
@@ -390,7 +390,8 @@
 3.6.0_1
 3.6.0
 5.5.0_1
-5.5.3
+
+5.5.0
 [5,6)
 0.1.8
 2.4
@@ -528,7 +529,8 @@
 1.1.2.6
 2.3.4_1
 5.5.0_1
-5.5.3
+
+5.5.0
 [5,6)
 1.6.1
 2.3

[GitHub] camel pull request #1170: [CAMEL-10311] Comprehensively define lucene artefa...

[tdiesler]

GitHub user tdiesler opened a pull request:

https://github.com/apache/camel/pull/1170

[CAMEL-10311] Comprehensively define lucene artefacts used by elastic…

…search

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tdiesler/camel CAMEL-10311

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1170.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1170


commit 29d46f9dcf4c83817dee12e542536f186090b014
Author: Thomas Diesler 
Date:   2016-09-12T10:27:05Z

[CAMEL-10311] Comprehensively define lucene artefacts used by elasticsearch




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Getting ready for Apache Camel 2.18 Release

[Nicola Ferraro]

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’s 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’ll get working on that to clean 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’t quite 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
> “good” test route and what you’d like to see happen for testing, I’d really
> like to see it and I’ll try and use that instead.
> 4)  I’m not sure where I came up with the name of the example - but you’re
> right - I’ll change it to example-camel-test-karaf
> 5) I’ll get back in and figure out why the integration test is failing now
> - I was certain they were working at one time.  Anyway, the unit tests pass
> - but they generate a bunch of scary messages in the log files.  I didn’t
> 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’d really like to
> hear them.
>
> I’ve got one other bug to fix, then I’ll get back on this one.
>
> If you wouldn’t mind “watching” 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.wal...@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 PR
> 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´s not the point of your sample but the timer-example seems a bit
> basic.
> > 4) maybe …-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 

[GitHub] camel pull request #1169: Fix broken scope tags

[jamesnetherton]

Github user jamesnetherton closed the pull request at:

https://github.com/apache/camel/pull/1169


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] camel pull request #1169: Fix broken scope tags

[jamesnetherton]

GitHub user jamesnetherton opened a pull request:

https://github.com/apache/camel/pull/1169

Fix broken scope tags



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jamesnetherton/camel pom-fix

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/1169.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1169


commit fb31a2be6c77b92a392c63fa61edcda7fca476d2
Author: James Netherton 
Date:   2016-09-12T07:29:56Z

Fix broken scope tags




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---