[GitHub] camel pull request #1181: Camel 10307: Upgrade docker java version

[Fabryprog]

GitHub user Fabryprog opened a pull request:

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

Camel 10307: Upgrade docker java version

https://issues.apache.org/jira/browse/CAMEL-10307

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

$ git pull https://github.com/Fabryprog/camel CAMEL-10307

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

https://github.com/apache/camel/pull/1181.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 #1181


commit 9979bbd174669cd431c122c4f5621818c510b9ea
Author: Fabrizio Spataro 
Date:   2016-09-19T16:28:43Z

CAMEL-10307, docker library upgrade (async test incomplete)

commit b6f521ea16ff4f0f638acb84ab9acfe2a9e88c37
Author: Fabryprog 
Date:   2016-09-19T22:29:47Z

CAMEL-10307, docker test (async) fixed!

commit ac7dd5314913a584ee9f1696de3d715bb677e636
Author: Fabrizio Spataro 
Date:   2016-09-20T08:10:23Z

CAMEL-10307, docker lib upgraded!




---
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 #1164: CAMEL-10222: New spring-boot BOM

[nicolaferraro]

Github user nicolaferraro closed the pull request at:

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


---
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 #1182: CAMEL-10222: Conflicts-free springboot BOM

[nicolaferraro]

GitHub user nicolaferraro opened a pull request:

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

CAMEL-10222: Conflicts-free springboot BOM

I created a camel BOM without conflicts with the spring-boot one, as 
discussed in the mailing list.
I removed the following modules from the list of starters (with reference 
to the previous PR):
- IBatis and Quartz (v1): deprecated and having many issues when running 
unit tests in sb mode
- Jclouds: Jclouds-core uses a specific version of Gson. Cannot work with 
the one in the spring-bom.
- SparkRest: Internally using a class that is missing in the version of 
Jetty used by spring-boot.

There are also other (10) modules having some problems, but issues might be 
caused by the testing environment. For example, the Cassandra module might work 
with v2 of the driver, but the tests cannot ensure this because unit tests 
include cassandra-all into the classpath and it is much more probable that 
cassandra-all cannot work in a spring-boot environment (and it must not).
I kept that starters, as they should work: Ahc, Cassandra, Consul, Jgroups, 
Jibx, Jpa, Xmljson, Mongodb, MongodbGridfs, Mybatis.

Waiting for feedbacks.

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

$ git pull https://github.com/nicolaferraro/camel CAMEL-10222-P3

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

https://github.com/apache/camel/pull/1182.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 #1182


commit 5ca0fda09cb3cea7a2d73ec6ff660afed7f18e6c
Author: Nicola Ferraro 
Date:   2016-09-01T10:41:55Z

CAMEL-10222: Fixed some poms up to HBase

commit 2c8e289bce4ed2c7dc540b6f3168c8f38bfade7e
Author: Nicola Ferraro 
Date:   2016-09-02T10:09:48Z

CAMEL-10222: Good configuration up to Jetty9

commit 7f351389f96e2d424964cd4506ff776b1f6e
Author: Nicola Ferraro 
Date:   2016-09-02T11:43:38Z

CAMEL-10222: Fixed resolution of wrong versions

commit 9de5089abe9640b7d15fc95d05a81b44f366c049
Author: Nicola Ferraro 
Date:   2016-09-06T10:09:54Z

CAMEL-10222: Added more stuff to the BOM

commit c39db2d390351807f4f0378b15d96bc3e7330e64
Author: Nicola Ferraro 
Date:   2016-09-06T10:17:41Z

CAMEL-10222: Stable version

commit f9c2a954f2efe0c5b09cc76e203c489c32ed261d
Author: Nicola Ferraro 
Date:   2016-09-06T15:36:11Z

CAMEL-10222: First generated BOM

commit b45ccadbd94371b2a3b25f964f04df8448e70595
Author: Nicola Ferraro 
Date:   2016-09-07T09:46:56Z

CAMEL-10222: First real BOM

commit 459b11fd34a6d59dbeb6eb8f9a78b6dc1eaf6cfd
Author: Nicola Ferraro 
Date:   2016-09-07T09:52:35Z

CAMEL-10222: Simpler BOM

commit 03a7e99bc6fc57ae98cea7ea5a62979466f2a1ea
Author: Nicola Ferraro 
Date:   2016-09-07T12:21:00Z

CAMEL-10222: Pre-test release

commit b12445607a8a1a8797e07bb35cb989cd1d160a35
Author: Nicola Ferraro 
Date:   2016-09-07T14:37:23Z

CAMEL-10222: First working version (no unit tests)

commit 08791341466686285b9a5e8c948379973be3f7ba
Author: Nicola Ferraro 
Date:   2016-09-08T09:52:32Z

CAMEL-10222: Fixing compatibility with Jetty 9.3 (provided with spring-boot)

commit 046156cee90232d04db857cff49390dae833bf97
Author: Nicola Ferraro 
Date:   2016-09-08T15:23:21Z

CAMEL-10222: Fixed several modules and starters

commit 993e57830eb2e79c81d3b6377c44389f54aa386c
Author: Nicola Ferraro 
Date:   2016-09-09T09:07:14Z

CAMEL-10222: Rewriting the examples to use the new spring-boot BOM

commit 107e6e80984c0b1d2b7deeaf983bc6622578ab5c
Author: Nicola Ferraro 
Date:   2016-09-09T09:30:55Z

CAMEL-10222: Rewriting the archetype to use the new BOM

commit 702dd979ebe1871ff256d128cb6935ef3ac3deee
Author: Nicola Ferraro 
Date:   2016-09-09T09:42:31Z

CAMEL-10222: Adding starters to the assembly

commit 2292d2d7bbca40878dc958ef68924ce9abec41ea
Author: Nicola Ferraro 
Date:   2016-09-09T09:53:01Z

CAMEL-10222: Simplified pom configuration

commit fc44cce212ff267a75448138d6f572a6f0e27488
Author: Nicola Ferraro 
Date:   2016-09-09T11:29:48Z

CAMEL-10222: Fixing scala and servlet starters

commit 923c44bcb1021cea632e47b77db775d60e82c59c
Author: Nicola Ferraro 
Date:   2016-09-09T12:29:16Z

CAMEL-10222: Aligning libraries with master

commit 281fbfd89142adbbfaca5b277af6f22550c36525
Author: Nicola Ferraro 
Date:   2016-09-09T13:17:46Z

CAMEL-10222: Source check

commit b1dfcabe3151286bc7096d796037a57baa9a002c
Author: Nicola Ferraro 

[GitHub] camel pull request #1181: Camel 10307: Upgrade docker java version

[Fabryprog]

Github user Fabryprog closed the pull request at:

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


---
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.
---

Blueprint and property placeholder

[dpravin]

Hello All,

We have some common properties, not integration/bundle specific. Can
multiple routes/bundles refer to these property files from blueprint using
cm:property-placeholder? 

I also found out that if you have set update-strategy="reload" the bundle
get restarted irrespective of the property being used by the bundle. Is this
the default behavior? Is there anything that can help avoid reload/restart
of bundle if the property is not used?

Thanks,
Pravin



--
View this message in context: 
http://camel.465427.n5.nabble.com/Blueprint-and-property-placeholder-tp5787762.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: Blueprint and property placeholder

[Grzegorz Grzybek]

Hello,

Please see technical details about property placeholders in Camel/Blueprint
here: http://ggrzybek.blogspot.com/2015/12/camel-blueprint-test-support.html
.

Can multiple routes/bundles refer to these property files from blueprint
> using cm:property-placeholder?
>

Routes - yes, if they're defined in single blueprint.xml / set of blueprint
XMLs in one bundle.

Bundles - I'm not sure. Bundle alone can have (easy) access to properties
defined in . What do you mean?

I also found out that if you have set update-strategy="reload" the bundle
> get restarted irrespective of the property being used by the bundle.


This setting means that if you update give PID (Persistence Identifier) -
any property within this PID, blueprint container containing
 will be restarted and
all the beans (including camel context, routes, ...) will be recreated with
new values of property placeholders.

The fact that some properties may not be used in your context/route
definition is irrelevant.

regards
Grzegorz Grzybek

2016-09-20 19:33 GMT+02:00 dpravin :

> Hello All,
>
> We have some common properties, not integration/bundle specific. Can
> multiple routes/bundles refer to these property files from blueprint using
> cm:property-placeholder?
>
> I also found out that if you have set update-strategy="reload" the bundle
> get restarted irrespective of the property being used by the bundle. Is
> this
> the default behavior? Is there anything that can help avoid reload/restart
> of bundle if the property is not used?
>
> Thanks,
> Pravin
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.
> com/Blueprint-and-property-placeholder-tp5787762.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>

Camel.trunk.notest - Build # 2880 - Failure

[Apache Jenkins Server]

The Apache Jenkins build system has built Camel.trunk.notest (build #2880)

Status: Failure

Check console output at https://builds.apache.org/job/Camel.trunk.notest/2880/ 
to view the results.

[GitHub] camel pull request #1183: [CAMEL-10332] Define netty version in dependency m...

[tdiesler]

GitHub user tdiesler opened a pull request:

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

[CAMEL-10332] Define netty version in dependency management



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

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

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

https://github.com/apache/camel/pull/1183.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 #1183


commit 3ddbeea1e970ad91d3227c5622a1eef190c3016e
Author: Thomas Diesler 
Date:   2016-09-20T14:24:00Z

[CAMEL-10332] Define netty version in dependency management




---
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.
---