Camel.trunk.notest - Build # 3172 - Fixed

[Apache Jenkins Server]

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

Status: Fixed

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

Re: Camel 2.19 Roadmap

[Gregor Zurowski]

Hi Everyone:

I am starting to cut the 2.19.0 RC now.

Thanks,
Gregor


On Mon, Apr 24, 2017 at 7:00 PM, Luca Burgazzoli  wrote:
> Hi Gregor,
>
> I've committed my fixes.
>
>
>
> ---
> Luca Burgazzoli
>
>
> On Mon, Apr 24, 2017 at 6:10 PM, Luca Burgazzoli  
> wrote:
>> Hi Gregor,
>>
>> I'm running a local build to see if there is any blocking issue some
>> JIRA I'd like to include [1][2][3], it should not take too much and
>> I'll post here as son  as I have merged my work on master.
>>
>>
>> [1] https://issues.apache.org/jira/browse/CAMEL-11190
>> [2] https://issues.apache.org/jira/browse/CAMEL-11191
>> [3] https://issues.apache.org/jira/browse/CAMEL-11192
>>
>>
>> ---
>> Luca Burgazzoli
>>
>>
>> On Mon, Apr 24, 2017 at 11:11 AM, Gregor Zurowski
>>  wrote:
>>> Hi Claus,
>>>
>>> Alright, I guess this is the best we can do for now.  I also agree on
>>> removing the regular examples from the release.  I would actually also
>>> move them into a separate artifact group.  Currently they use the
>>> group ID org.apache.camel, so we could move them into
>>> org.apache.camel.example or similar.
>>>
>>> I will re-cut the release candidate tonight.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Mon, Apr 24, 2017 at 10:49 AM, Claus Ibsen  wrote:
 Hi Gregor

 So we have now fixed this by turning of those connector examples as
 they should not be in the release.

 We will later re-organize this and see what to do if any of this is
 needed as releases JAR in maven central.
 You could consider the same for the regular examples, they should
 maybe not be released either to maven central.
 But its a talk for another day.

 The master branch should be ready for a re-cut of the release.

 Let us know when you are able to work on this again. Thanks a lot for
 helping with the releases.








 On Mon, Apr 24, 2017 at 10:22 AM, Claus Ibsen  
 wrote:
> Hi Gregor
>
> Okay so the connector examples are not yet intended for release (if
> they ever would be).
> So I have skipped them.
>
> People can try them from the source code as they do with the other
> examples. That works fine.
>
> For a release process we may also need to add some extra logic so the
> SNAPSHOT versions in the json files etc are replaced as part of a
> release build. AFAIR you need to run 2 x build, to make it updated,
> which you can't usually.
>
>
>
> On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
>  wrote:
>> Hi Everyone:
>>
>> I have finally managed to resolve all memory-related and
>> machine-related issues, but I am hitting another road block in the
>> release process.  The process fails when the new connector examples
>> are about to get pushed to the artifact repository:
>>
>> [INFO] [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
>> (default-deploy) on project beverage-component: Failed to deploy
>> artifacts: Could not transfer artifact
>> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
>> (https://repository.apache.org/service/local/staging/deploy/maven2):
>> Failed to transfer file:
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>>
>> This is likely caused by the group ID "org.foo" that is used in these
>> modules, which will not be accepted by the Apache artifact repository.
>>
>> I could easily change the group ID of these examples to something like
>> "org.apache.camel.example.connector".  While attempting to change
>> this, I realized that there are JSON files in the example directories
>> that directly reference these artifacts, for example in
>> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>>
>>   "groupId" : "org.foo",
>>   "artifactId" : "salesforce-upsert-contact-connector",
>>   "version" : "2.19.0-SNAPSHOT"
>>
>> I can update the group ID here as well, but the release process is not
>> prepared to handle any of these JSON files for updating the version
>> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
>> within the release preparation step.
>>
>> Please let me know how to proceed here.  Once we resolve this, I will
>> restart the release.
>>
>> Thanks,
>> Gregor
>>
>>
>> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen  
>> wrote:
>>> Hi Gregor
>>>
>>> Sorry for adding that CS error this morning. I guess the extra text in
>>> that exception message may have 

Re: Camel 2.19 Roadmap

[Luca Burgazzoli]

Hi Gregor,

I've committed my fixes.



---
Luca Burgazzoli


On Mon, Apr 24, 2017 at 6:10 PM, Luca Burgazzoli  wrote:
> Hi Gregor,
>
> I'm running a local build to see if there is any blocking issue some
> JIRA I'd like to include [1][2][3], it should not take too much and
> I'll post here as son  as I have merged my work on master.
>
>
> [1] https://issues.apache.org/jira/browse/CAMEL-11190
> [2] https://issues.apache.org/jira/browse/CAMEL-11191
> [3] https://issues.apache.org/jira/browse/CAMEL-11192
>
>
> ---
> Luca Burgazzoli
>
>
> On Mon, Apr 24, 2017 at 11:11 AM, Gregor Zurowski
>  wrote:
>> Hi Claus,
>>
>> Alright, I guess this is the best we can do for now.  I also agree on
>> removing the regular examples from the release.  I would actually also
>> move them into a separate artifact group.  Currently they use the
>> group ID org.apache.camel, so we could move them into
>> org.apache.camel.example or similar.
>>
>> I will re-cut the release candidate tonight.
>>
>> Thanks,
>> Gregor
>>
>>
>> On Mon, Apr 24, 2017 at 10:49 AM, Claus Ibsen  wrote:
>>> Hi Gregor
>>>
>>> So we have now fixed this by turning of those connector examples as
>>> they should not be in the release.
>>>
>>> We will later re-organize this and see what to do if any of this is
>>> needed as releases JAR in maven central.
>>> You could consider the same for the regular examples, they should
>>> maybe not be released either to maven central.
>>> But its a talk for another day.
>>>
>>> The master branch should be ready for a re-cut of the release.
>>>
>>> Let us know when you are able to work on this again. Thanks a lot for
>>> helping with the releases.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Apr 24, 2017 at 10:22 AM, Claus Ibsen  wrote:
 Hi Gregor

 Okay so the connector examples are not yet intended for release (if
 they ever would be).
 So I have skipped them.

 People can try them from the source code as they do with the other
 examples. That works fine.

 For a release process we may also need to add some extra logic so the
 SNAPSHOT versions in the json files etc are replaced as part of a
 release build. AFAIR you need to run 2 x build, to make it updated,
 which you can't usually.



 On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
  wrote:
> Hi Everyone:
>
> I have finally managed to resolve all memory-related and
> machine-related issues, but I am hitting another road block in the
> release process.  The process fails when the new connector examples
> are about to get pushed to the artifact repository:
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy) on project beverage-component: Failed to deploy
> artifacts: Could not transfer artifact
> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
> (https://repository.apache.org/service/local/staging/deploy/maven2):
> Failed to transfer file:
> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>
> This is likely caused by the group ID "org.foo" that is used in these
> modules, which will not be accepted by the Apache artifact repository.
>
> I could easily change the group ID of these examples to something like
> "org.apache.camel.example.connector".  While attempting to change
> this, I realized that there are JSON files in the example directories
> that directly reference these artifacts, for example in
> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>
>   "groupId" : "org.foo",
>   "artifactId" : "salesforce-upsert-contact-connector",
>   "version" : "2.19.0-SNAPSHOT"
>
> I can update the group ID here as well, but the release process is not
> prepared to handle any of these JSON files for updating the version
> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
> within the release preparation step.
>
> Please let me know how to proceed here.  Once we resolve this, I will
> restart the release.
>
> Thanks,
> Gregor
>
>
> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen  
> wrote:
>> Hi Gregor
>>
>> Sorry for adding that CS error this morning. I guess the extra text in
>> that exception message may have caused the line to be too long?
>>
>> I noticed some Maven WARNs about some examples was a bit wrong with
>> bundle vs jar. So I aligned them and just pushed.
>> I will step away from the computer so you should have a quiet time to
>> work on the release.
>>
>>
>>

Re: Camel 2.19 Roadmap

[Luca Burgazzoli]

Hi Gregor,

I'm running a local build to see if there is any blocking issue some
JIRA I'd like to include [1][2][3], it should not take too much and
I'll post here as son  as I have merged my work on master.


[1] https://issues.apache.org/jira/browse/CAMEL-11190
[2] https://issues.apache.org/jira/browse/CAMEL-11191
[3] https://issues.apache.org/jira/browse/CAMEL-11192


---
Luca Burgazzoli


On Mon, Apr 24, 2017 at 11:11 AM, Gregor Zurowski
 wrote:
> Hi Claus,
>
> Alright, I guess this is the best we can do for now.  I also agree on
> removing the regular examples from the release.  I would actually also
> move them into a separate artifact group.  Currently they use the
> group ID org.apache.camel, so we could move them into
> org.apache.camel.example or similar.
>
> I will re-cut the release candidate tonight.
>
> Thanks,
> Gregor
>
>
> On Mon, Apr 24, 2017 at 10:49 AM, Claus Ibsen  wrote:
>> Hi Gregor
>>
>> So we have now fixed this by turning of those connector examples as
>> they should not be in the release.
>>
>> We will later re-organize this and see what to do if any of this is
>> needed as releases JAR in maven central.
>> You could consider the same for the regular examples, they should
>> maybe not be released either to maven central.
>> But its a talk for another day.
>>
>> The master branch should be ready for a re-cut of the release.
>>
>> Let us know when you are able to work on this again. Thanks a lot for
>> helping with the releases.
>>
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Apr 24, 2017 at 10:22 AM, Claus Ibsen  wrote:
>>> Hi Gregor
>>>
>>> Okay so the connector examples are not yet intended for release (if
>>> they ever would be).
>>> So I have skipped them.
>>>
>>> People can try them from the source code as they do with the other
>>> examples. That works fine.
>>>
>>> For a release process we may also need to add some extra logic so the
>>> SNAPSHOT versions in the json files etc are replaced as part of a
>>> release build. AFAIR you need to run 2 x build, to make it updated,
>>> which you can't usually.
>>>
>>>
>>>
>>> On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
>>>  wrote:
 Hi Everyone:

 I have finally managed to resolve all memory-related and
 machine-related issues, but I am hitting another road block in the
 release process.  The process fails when the new connector examples
 are about to get pushed to the artifact repository:

 [INFO] [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
 (default-deploy) on project beverage-component: Failed to deploy
 artifacts: Could not transfer artifact
 org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
 (https://repository.apache.org/service/local/staging/deploy/maven2):
 Failed to transfer file:
 https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
 Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]

 This is likely caused by the group ID "org.foo" that is used in these
 modules, which will not be accepted by the Apache artifact repository.

 I could easily change the group ID of these examples to something like
 "org.apache.camel.example.connector".  While attempting to change
 this, I realized that there are JSON files in the example directories
 that directly reference these artifacts, for example in
 /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:

   "groupId" : "org.foo",
   "artifactId" : "salesforce-upsert-contact-connector",
   "version" : "2.19.0-SNAPSHOT"

 I can update the group ID here as well, but the release process is not
 prepared to handle any of these JSON files for updating the version
 elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
 within the release preparation step.

 Please let me know how to proceed here.  Once we resolve this, I will
 restart the release.

 Thanks,
 Gregor


 On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen  wrote:
> Hi Gregor
>
> Sorry for adding that CS error this morning. I guess the extra text in
> that exception message may have caused the line to be too long?
>
> I noticed some Maven WARNs about some examples was a bit wrong with
> bundle vs jar. So I aligned them and just pushed.
> I will step away from the computer so you should have a quiet time to
> work on the release.
>
>
>
>
> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
>  wrote:
>> Hi Claus,
>>
>> I am still working on the release, just found some CS issues.
>>
>> I am using a different box now, because the OOME problems were
>> definitely 

[GitHub] camel pull request #1656: CAMEL-11194 Upgrade Checkstyle and update rules

[zregvart]

GitHub user zregvart opened a pull request:

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

CAMEL-11194 Upgrade Checkstyle and update rules

This upgrades Checkstyle to the latest version currently available, refines 
the way license header in properties files are handled and sets the execution 
id of Checkstyle Maven plugin to `default-cli` so that the checks can be simply 
run with:

mvn checkstyle:check

Changes are split into multiple commits to make it easier to review.

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

$ git pull https://github.com/zregvart/camel CAMEL-11194

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

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


commit c3bba7ae6d980448f1153c4f0c96755838c314e1
Author: Claus Ibsen 
Date:   2017-04-23T11:13:51Z

Fixed license header

commit cf8670e7d643b3fe07776c974840ea0b78060093
Author: Jonathan Schoreels 
Date:   2017-04-23T13:52:22Z

JdbcAggregationRepository : Adds some javadoc to clearly specify that 
properties are NOT persisted, and other properties as described in 
camel.apache.org

commit 3bf9847506cc0f963e3d5b0c6bc7774b0aab3f4e
Author: Jonathan Schoreels 
Date:   2017-04-23T14:07:53Z

Adds JdbcAggregationRepository java doc to make clear that deadletter will 
be tried until it succeed

commit a4d2334ce7b95a964d1f029b5188818793118e8d
Author: Claus Ibsen 
Date:   2017-04-24T07:44:46Z

Merge branch 'master' of https://github.com/JSchoreels/camel

commit 820410e2186a0135eab041de0f0e58843d21731c
Author: Claus Ibsen 
Date:   2017-04-24T08:17:29Z

Skip connector examples as they are not intended for release.

commit 7a511ef5230b7447957e27a6082a6ac5e85e2f9f
Author: Chirag Anand 
Date:   2017-04-24T05:13:08Z

Added the provision to pass Solr Params when pushing SolrInputDocuments.

This change is necessary when you intend to have an update processor chain 
to be trigerred or any such for which parameters are to be passed along with 
the url.

commit d01dc3e345aad763db9a5e9c736df6727b65
Author: Claus Ibsen 
Date:   2017-04-24T08:30:53Z

CAMEL-11185: Remove camel-scr-starter spring boot module

commit bab5b27bce8d9d799cfa4c77a1bfd1a1c023d281
Author: Claus Ibsen 
Date:   2017-04-24T08:46:47Z

CAMEL-11189: Upgrade zipkin

commit 1d164d54675069fb672be606e99c2c7944cd8f23
Author: Claus Ibsen 
Date:   2017-04-24T11:03:56Z

CAMEL-1193: Make kafka easier to use when routing between topics to avoid 
the header topic causing Camel to send the message to itself instead of the 
endpoint topic name as users would expect.

commit 8b5e93ec694ef31a2bd43248735d3bc274f4e9d3
Author: Claus Ibsen 
Date:   2017-04-24T11:24:20Z

Make kafka bridgeEndpoint option on configuraion so they are all there and 
thus also available via spring boot

commit 6243402b2291af99c7f7b950f5e905489d403074
Author: Claus Ibsen 
Date:   2017-04-24T11:29:33Z

Add some logging in kafka producer when it sends/has all sent etc.

commit 97ecc14735765749fdba823acf5e9ba1a5628424
Author: Claus Ibsen 
Date:   2017-04-24T11:40:33Z

Logging level to info as debug is massiively verbose

commit 3ffd940a70994c9810b7b915d7a336fd8ad689cb
Author: Claus Ibsen 
Date:   2017-04-24T11:51:15Z

CAMEL-11186: upgrade dropwizard metrics to align with Spring Boot

commit 27517e78e4ffcfafb502f1c863bc0d8aede871bc
Author: Zoran Regvart 
Date:   2017-04-24T11:46:12Z

CAMEL-11194 Upgrade Checkstyle and update rules

This updates the Checkstyle version to 7.6.1, it also changes the
execution id from `validate` to `default-cli` which allows the
Checkstyle Maven plugin to be run with just `mvn checkstyle:check`.

The change in Checkstyle rules now allows for different header comment
on source files and on properties files. The rule that affects the use
of `final` keyword and the rule that checks the `return` statement count
per method were tweaked to reflect the current code base.

commit 13b0c17d865d15f06300f9cde317b1581b962c48
Author: Zoran Regvart 
Date:   2017-04-24T11:45:21Z

CAMEL-11194 Upgrade Checkstyle and update rules

This updates the license header in properties files.

commit 5bfe72d54bb86deb8630985091aad540743178fa
Author: Zoran Regvart 
Date:   2017-04-24T11:48:23Z

CAMEL-11194 Upgrade Checkstyle and update rules

Changes the formatting of Spring Boot auto configuration starters to use

Add yourself to Camel bloggers and tweeters

[Claus Ibsen]

Hi

If you blog and tweet about Apache Camel then you are welcome to add
yourself to our link collection at
https://cwiki.apache.org/confluence/display/CAMEL/Articles

In the bottom we have links to blogs and twitters.


-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Apache Camel 2.19 release blog posts and help spread the word

[Andrea Cosentino]

Great idea! I can write something :-)
 
--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd


On Monday, April 24, 2017 2:15 PM, Claus Ibsen  wrote:



Hi


When the new 2.19 release is out the door, it would be good if we

could spread the word about this release with a number of blogs posts,

twitter, and publish articles on websites etc.


For that we may need a general blog post with the news and a summary

of the top 10 most noteworthy features/changes. I have done some of

those in the past (such as

http://www.davsclaus.com/2016/10/apache-camel-218-released-whats-included.html).


And then maybe some blog posts that are a specific about one

functionality, such as Luca's recent about service call for cloud,

etc.


Any thoughts?



-- 

Claus Ibsen

-

http://davsclaus.com @davsclaus

Camel in Action 2: https://www.manning.com/ibsen2

Apache Camel 2.19 release blog posts and help spread the word

[Claus Ibsen]

Hi

When the new 2.19 release is out the door, it would be good if we
could spread the word about this release with a number of blogs posts,
twitter, and publish articles on websites etc.

For that we may need a general blog post with the news and a summary
of the top 10 most noteworthy features/changes. I have done some of
those in the past (such as
http://www.davsclaus.com/2016/10/apache-camel-218-released-whats-included.html).

And then maybe some blog posts that are a specific about one
functionality, such as Luca's recent about service call for cloud,
etc.

Any thoughts?


-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel 2.19 Roadmap

[Gregor Zurowski]

Hi Claus,

Alright, I guess this is the best we can do for now.  I also agree on
removing the regular examples from the release.  I would actually also
move them into a separate artifact group.  Currently they use the
group ID org.apache.camel, so we could move them into
org.apache.camel.example or similar.

I will re-cut the release candidate tonight.

Thanks,
Gregor


On Mon, Apr 24, 2017 at 10:49 AM, Claus Ibsen  wrote:
> Hi Gregor
>
> So we have now fixed this by turning of those connector examples as
> they should not be in the release.
>
> We will later re-organize this and see what to do if any of this is
> needed as releases JAR in maven central.
> You could consider the same for the regular examples, they should
> maybe not be released either to maven central.
> But its a talk for another day.
>
> The master branch should be ready for a re-cut of the release.
>
> Let us know when you are able to work on this again. Thanks a lot for
> helping with the releases.
>
>
>
>
>
>
>
>
> On Mon, Apr 24, 2017 at 10:22 AM, Claus Ibsen  wrote:
>> Hi Gregor
>>
>> Okay so the connector examples are not yet intended for release (if
>> they ever would be).
>> So I have skipped them.
>>
>> People can try them from the source code as they do with the other
>> examples. That works fine.
>>
>> For a release process we may also need to add some extra logic so the
>> SNAPSHOT versions in the json files etc are replaced as part of a
>> release build. AFAIR you need to run 2 x build, to make it updated,
>> which you can't usually.
>>
>>
>>
>> On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
>>  wrote:
>>> Hi Everyone:
>>>
>>> I have finally managed to resolve all memory-related and
>>> machine-related issues, but I am hitting another road block in the
>>> release process.  The process fails when the new connector examples
>>> are about to get pushed to the artifact repository:
>>>
>>> [INFO] [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
>>> (default-deploy) on project beverage-component: Failed to deploy
>>> artifacts: Could not transfer artifact
>>> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
>>> (https://repository.apache.org/service/local/staging/deploy/maven2):
>>> Failed to transfer file:
>>> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
>>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>>>
>>> This is likely caused by the group ID "org.foo" that is used in these
>>> modules, which will not be accepted by the Apache artifact repository.
>>>
>>> I could easily change the group ID of these examples to something like
>>> "org.apache.camel.example.connector".  While attempting to change
>>> this, I realized that there are JSON files in the example directories
>>> that directly reference these artifacts, for example in
>>> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>>>
>>>   "groupId" : "org.foo",
>>>   "artifactId" : "salesforce-upsert-contact-connector",
>>>   "version" : "2.19.0-SNAPSHOT"
>>>
>>> I can update the group ID here as well, but the release process is not
>>> prepared to handle any of these JSON files for updating the version
>>> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
>>> within the release preparation step.
>>>
>>> Please let me know how to proceed here.  Once we resolve this, I will
>>> restart the release.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen  wrote:
 Hi Gregor

 Sorry for adding that CS error this morning. I guess the extra text in
 that exception message may have caused the line to be too long?

 I noticed some Maven WARNs about some examples was a bit wrong with
 bundle vs jar. So I aligned them and just pushed.
 I will step away from the computer so you should have a quiet time to
 work on the release.




 On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
  wrote:
> Hi Claus,
>
> I am still working on the release, just found some CS issues.
>
> I am using a different box now, because the OOME problems were
> definitely caused by some issues with the machine I was using
> previously.
>
> Will keep you posted.
>
> Thanks,
> Gregor
>
>
> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen  
> wrote:
>> Hi
>>
>> Building the release candidate takes up a lot of memory and Gregor has
>> hit a OOME with 6gb.
>>
>> We are cleaning up a bit in the project to upgrade some of the maven
>> plugins to use newer versions and reduce some cruft in the assembly.
>>
>>
>>
>> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen 

[GitHub] camel pull request #1655: [CAMEL-11182]SolrParams are not honored when sendi...

[chirag0103]

Github user chirag0103 closed the pull request at:

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


---
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 2.19 Roadmap

[Claus Ibsen]

Hi Gregor

So we have now fixed this by turning of those connector examples as
they should not be in the release.

We will later re-organize this and see what to do if any of this is
needed as releases JAR in maven central.
You could consider the same for the regular examples, they should
maybe not be released either to maven central.
But its a talk for another day.

The master branch should be ready for a re-cut of the release.

Let us know when you are able to work on this again. Thanks a lot for
helping with the releases.








On Mon, Apr 24, 2017 at 10:22 AM, Claus Ibsen  wrote:
> Hi Gregor
>
> Okay so the connector examples are not yet intended for release (if
> they ever would be).
> So I have skipped them.
>
> People can try them from the source code as they do with the other
> examples. That works fine.
>
> For a release process we may also need to add some extra logic so the
> SNAPSHOT versions in the json files etc are replaced as part of a
> release build. AFAIR you need to run 2 x build, to make it updated,
> which you can't usually.
>
>
>
> On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
>  wrote:
>> Hi Everyone:
>>
>> I have finally managed to resolve all memory-related and
>> machine-related issues, but I am hitting another road block in the
>> release process.  The process fails when the new connector examples
>> are about to get pushed to the artifact repository:
>>
>> [INFO] [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
>> (default-deploy) on project beverage-component: Failed to deploy
>> artifacts: Could not transfer artifact
>> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
>> (https://repository.apache.org/service/local/staging/deploy/maven2):
>> Failed to transfer file:
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>>
>> This is likely caused by the group ID "org.foo" that is used in these
>> modules, which will not be accepted by the Apache artifact repository.
>>
>> I could easily change the group ID of these examples to something like
>> "org.apache.camel.example.connector".  While attempting to change
>> this, I realized that there are JSON files in the example directories
>> that directly reference these artifacts, for example in
>> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>>
>>   "groupId" : "org.foo",
>>   "artifactId" : "salesforce-upsert-contact-connector",
>>   "version" : "2.19.0-SNAPSHOT"
>>
>> I can update the group ID here as well, but the release process is not
>> prepared to handle any of these JSON files for updating the version
>> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
>> within the release preparation step.
>>
>> Please let me know how to proceed here.  Once we resolve this, I will
>> restart the release.
>>
>> Thanks,
>> Gregor
>>
>>
>> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen  wrote:
>>> Hi Gregor
>>>
>>> Sorry for adding that CS error this morning. I guess the extra text in
>>> that exception message may have caused the line to be too long?
>>>
>>> I noticed some Maven WARNs about some examples was a bit wrong with
>>> bundle vs jar. So I aligned them and just pushed.
>>> I will step away from the computer so you should have a quiet time to
>>> work on the release.
>>>
>>>
>>>
>>>
>>> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
>>>  wrote:
 Hi Claus,

 I am still working on the release, just found some CS issues.

 I am using a different box now, because the OOME problems were
 definitely caused by some issues with the machine I was using
 previously.

 Will keep you posted.

 Thanks,
 Gregor


 On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen  
 wrote:
> Hi
>
> Building the release candidate takes up a lot of memory and Gregor has
> hit a OOME with 6gb.
>
> We are cleaning up a bit in the project to upgrade some of the maven
> plugins to use newer versions and reduce some cruft in the assembly.
>
>
>
> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen  
> wrote:
>> Hi
>>
>> Looking at the CI tests then they all look good (blue/green)
>> https://builds.apache.org/view/A-D/view/Camel/
>>
>> .. except for the spring-boot tests which had two tests for
>> camel-core-xml and camel-spring-dm which does not make sense at all so
>> I have removed them. This should make this job blue as well.
>>
>>
>> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen  
>> wrote:
>>> Hi Gregor
>>>
>>> I can see you committed some fixed last evening.
>>>
>>> Do you 

Re: Camel 2.19 Roadmap

[Claus Ibsen]

Hi Gregor

Okay so the connector examples are not yet intended for release (if
they ever would be).
So I have skipped them.

People can try them from the source code as they do with the other
examples. That works fine.

For a release process we may also need to add some extra logic so the
SNAPSHOT versions in the json files etc are replaced as part of a
release build. AFAIR you need to run 2 x build, to make it updated,
which you can't usually.



On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
 wrote:
> Hi Everyone:
>
> I have finally managed to resolve all memory-related and
> machine-related issues, but I am hitting another road block in the
> release process.  The process fails when the new connector examples
> are about to get pushed to the artifact repository:
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy) on project beverage-component: Failed to deploy
> artifacts: Could not transfer artifact
> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
> (https://repository.apache.org/service/local/staging/deploy/maven2):
> Failed to transfer file:
> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>
> This is likely caused by the group ID "org.foo" that is used in these
> modules, which will not be accepted by the Apache artifact repository.
>
> I could easily change the group ID of these examples to something like
> "org.apache.camel.example.connector".  While attempting to change
> this, I realized that there are JSON files in the example directories
> that directly reference these artifacts, for example in
> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>
>   "groupId" : "org.foo",
>   "artifactId" : "salesforce-upsert-contact-connector",
>   "version" : "2.19.0-SNAPSHOT"
>
> I can update the group ID here as well, but the release process is not
> prepared to handle any of these JSON files for updating the version
> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
> within the release preparation step.
>
> Please let me know how to proceed here.  Once we resolve this, I will
> restart the release.
>
> Thanks,
> Gregor
>
>
> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen  wrote:
>> Hi Gregor
>>
>> Sorry for adding that CS error this morning. I guess the extra text in
>> that exception message may have caused the line to be too long?
>>
>> I noticed some Maven WARNs about some examples was a bit wrong with
>> bundle vs jar. So I aligned them and just pushed.
>> I will step away from the computer so you should have a quiet time to
>> work on the release.
>>
>>
>>
>>
>> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
>>  wrote:
>>> Hi Claus,
>>>
>>> I am still working on the release, just found some CS issues.
>>>
>>> I am using a different box now, because the OOME problems were
>>> definitely caused by some issues with the machine I was using
>>> previously.
>>>
>>> Will keep you posted.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen  wrote:
 Hi

 Building the release candidate takes up a lot of memory and Gregor has
 hit a OOME with 6gb.

 We are cleaning up a bit in the project to upgrade some of the maven
 plugins to use newer versions and reduce some cruft in the assembly.



 On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen  wrote:
> Hi
>
> Looking at the CI tests then they all look good (blue/green)
> https://builds.apache.org/view/A-D/view/Camel/
>
> .. except for the spring-boot tests which had two tests for
> camel-core-xml and camel-spring-dm which does not make sense at all so
> I have removed them. This should make this job blue as well.
>
>
> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen  
> wrote:
>> Hi Gregor
>>
>> I can see you committed some fixed last evening.
>>
>> Do you think that you found all the "bugs" in terms of building a
>> release candidate, or do we have more problems?
>>
>>
>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>>  wrote:
>>> Hi Claus,
>>>
>>> Thanks for taking care of this.  I will start building the release
>>> candidate now.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen  
>>> wrote:
 Hi

 I have just pushed fixes for RAT license check and CS checkstyle. They
 all pass now.
 I also added a few missing JARs in the release kit (the big
 zip/tarball with all the JARs)

Re: Camel 2.19 Roadmap

[Claus Ibsen]

Hi

I think you would need to deploy them if you build them locally, so
they can find it in the local m2 repo.

We deploy and ship all the examples
https://github.com/apache/camel/tree/master/examples

... which end up in maven central.
http://search.maven.org/#search%7Cga%7C1%7Ccamel-example





On Mon, Apr 24, 2017 at 9:55 AM, Zoran Regvart  wrote:
> Hi Gregor & Claus,
> I don't see much use for exaples in the repository, would the
> pragmatic solution be not to publish examples to the repository at
> all? We can skip the deploy plugin[1] it in the examples and
> connector-examples POMs?
>
> zoran
>
> [1] https://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
> --
> Zoran Regvart



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

[GitHub] camel pull request #1654: Adds javadoc to JDBCAggregationRepository

[JSchoreels]

Github user JSchoreels closed the pull request at:

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


---
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 2.19 Roadmap

[Zoran Regvart]

Hi Gregor & Claus,
I don't see much use for exaples in the repository, would the
pragmatic solution be not to publish examples to the repository at
all? We can skip the deploy plugin[1] it in the examples and
connector-examples POMs?

zoran

[1] https://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
-- 
Zoran Regvart

Re: Camel 2.19 Roadmap

[Claus Ibsen]

Hi Gregor

I will take a look at this, and report back.

On Sun, Apr 23, 2017 at 10:25 PM, Gregor Zurowski
 wrote:
> Hi Everyone:
>
> I have finally managed to resolve all memory-related and
> machine-related issues, but I am hitting another road block in the
> release process.  The process fails when the new connector examples
> are about to get pushed to the artifact repository:
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> (default-deploy) on project beverage-component: Failed to deploy
> artifacts: Could not transfer artifact
> org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
> (https://repository.apache.org/service/local/staging/deploy/maven2):
> Failed to transfer file:
> https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>
> This is likely caused by the group ID "org.foo" that is used in these
> modules, which will not be accepted by the Apache artifact repository.
>
> I could easily change the group ID of these examples to something like
> "org.apache.camel.example.connector".  While attempting to change
> this, I realized that there are JSON files in the example directories
> that directly reference these artifacts, for example in
> /salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:
>
>   "groupId" : "org.foo",
>   "artifactId" : "salesforce-upsert-contact-connector",
>   "version" : "2.19.0-SNAPSHOT"
>
> I can update the group ID here as well, but the release process is not
> prepared to handle any of these JSON files for updating the version
> elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
> within the release preparation step.
>
> Please let me know how to proceed here.  Once we resolve this, I will
> restart the release.
>
> Thanks,
> Gregor
>
>
> On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen  wrote:
>> Hi Gregor
>>
>> Sorry for adding that CS error this morning. I guess the extra text in
>> that exception message may have caused the line to be too long?
>>
>> I noticed some Maven WARNs about some examples was a bit wrong with
>> bundle vs jar. So I aligned them and just pushed.
>> I will step away from the computer so you should have a quiet time to
>> work on the release.
>>
>>
>>
>>
>> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
>>  wrote:
>>> Hi Claus,
>>>
>>> I am still working on the release, just found some CS issues.
>>>
>>> I am using a different box now, because the OOME problems were
>>> definitely caused by some issues with the machine I was using
>>> previously.
>>>
>>> Will keep you posted.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen  wrote:
 Hi

 Building the release candidate takes up a lot of memory and Gregor has
 hit a OOME with 6gb.

 We are cleaning up a bit in the project to upgrade some of the maven
 plugins to use newer versions and reduce some cruft in the assembly.



 On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen  wrote:
> Hi
>
> Looking at the CI tests then they all look good (blue/green)
> https://builds.apache.org/view/A-D/view/Camel/
>
> .. except for the spring-boot tests which had two tests for
> camel-core-xml and camel-spring-dm which does not make sense at all so
> I have removed them. This should make this job blue as well.
>
>
> On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen  
> wrote:
>> Hi Gregor
>>
>> I can see you committed some fixed last evening.
>>
>> Do you think that you found all the "bugs" in terms of building a
>> release candidate, or do we have more problems?
>>
>>
>> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>>  wrote:
>>> Hi Claus,
>>>
>>> Thanks for taking care of this.  I will start building the release
>>> candidate now.
>>>
>>> Thanks,
>>> Gregor
>>>
>>>
>>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen  
>>> wrote:
 Hi

 I have just pushed fixes for RAT license check and CS checkstyle. They
 all pass now.
 I also added a few missing JARs in the release kit (the big
 zip/tarball with all the JARs)



 On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
  wrote:
> Hi Everyone,
>
> That is great to hear, I will create the release candidate over the
> weekend, if all fixes are available on the master branch.
>
> Thanks,
> Gregor
>
> On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart 

Re: Camel 2.19 Roadmap

[Gregor Zurowski]

Hi Everyone:

I have finally managed to resolve all memory-related and
machine-related issues, but I am hitting another road block in the
release process.  The process fails when the new connector examples
are about to get pushed to the artifact repository:

[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
(default-deploy) on project beverage-component: Failed to deploy
artifacts: Could not transfer artifact
org.foo:beverage-component:jar:2.19.0 from/to apache.releases.https
(https://repository.apache.org/service/local/staging/deploy/maven2):
Failed to transfer file:
https://repository.apache.org/service/local/staging/deploy/maven2/org/foo/beverage-component/2.19.0/beverage-component-2.19.0.jar.
Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]

This is likely caused by the group ID "org.foo" that is used in these
modules, which will not be accepted by the Apache artifact repository.

I could easily change the group ID of these examples to something like
"org.apache.camel.example.connector".  While attempting to change
this, I realized that there are JSON files in the example directories
that directly reference these artifacts, for example in
/salesforce-upsert-contact-connector/src/main/resources/camel-connector.json:

  "groupId" : "org.foo",
  "artifactId" : "salesforce-upsert-contact-connector",
  "version" : "2.19.0-SNAPSHOT"

I can update the group ID here as well, but the release process is not
prepared to handle any of these JSON files for updating the version
elements, i.e. 2.19.0-SNAPSHOT should have been rewritten to 2.19.0
within the release preparation step.

Please let me know how to proceed here.  Once we resolve this, I will
restart the release.

Thanks,
Gregor


On Sat, Apr 22, 2017 at 3:00 PM, Claus Ibsen  wrote:
> Hi Gregor
>
> Sorry for adding that CS error this morning. I guess the extra text in
> that exception message may have caused the line to be too long?
>
> I noticed some Maven WARNs about some examples was a bit wrong with
> bundle vs jar. So I aligned them and just pushed.
> I will step away from the computer so you should have a quiet time to
> work on the release.
>
>
>
>
> On Sat, Apr 22, 2017 at 2:52 PM, Gregor Zurowski
>  wrote:
>> Hi Claus,
>>
>> I am still working on the release, just found some CS issues.
>>
>> I am using a different box now, because the OOME problems were
>> definitely caused by some issues with the machine I was using
>> previously.
>>
>> Will keep you posted.
>>
>> Thanks,
>> Gregor
>>
>>
>> On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen  wrote:
>>> Hi
>>>
>>> Building the release candidate takes up a lot of memory and Gregor has
>>> hit a OOME with 6gb.
>>>
>>> We are cleaning up a bit in the project to upgrade some of the maven
>>> plugins to use newer versions and reduce some cruft in the assembly.
>>>
>>>
>>>
>>> On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen  wrote:
 Hi

 Looking at the CI tests then they all look good (blue/green)
 https://builds.apache.org/view/A-D/view/Camel/

 .. except for the spring-boot tests which had two tests for
 camel-core-xml and camel-spring-dm which does not make sense at all so
 I have removed them. This should make this job blue as well.


 On Sat, Apr 22, 2017 at 9:13 AM, Claus Ibsen  wrote:
> Hi Gregor
>
> I can see you committed some fixed last evening.
>
> Do you think that you found all the "bugs" in terms of building a
> release candidate, or do we have more problems?
>
>
> On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
>  wrote:
>> Hi Claus,
>>
>> Thanks for taking care of this.  I will start building the release
>> candidate now.
>>
>> Thanks,
>> Gregor
>>
>>
>> On Fri, Apr 21, 2017 at 9:11 PM, Claus Ibsen  
>> wrote:
>>> Hi
>>>
>>> I have just pushed fixes for RAT license check and CS checkstyle. They
>>> all pass now.
>>> I also added a few missing JARs in the release kit (the big
>>> zip/tarball with all the JARs)
>>>
>>>
>>>
>>> On Fri, Apr 21, 2017 at 2:51 PM, Gregor Zurowski
>>>  wrote:
 Hi Everyone,

 That is great to hear, I will create the release candidate over the
 weekend, if all fixes are available on the master branch.

 Thanks,
 Gregor

 On Fri, Apr 21, 2017 at 1:59 PM, Zoran Regvart  
 wrote:
> Hi Cameleers,
> Andrea and Dmitry reviewed CAMEL-11181 and it was just pushed to 
> master,
>
> thank you :)
>
> zoran
>
> On Fri, Apr 21, 2017 at 1:32 PM, Claus Ibsen  
> wrote: