Camel.trunk.notest - Build # 2843 - Still Failing

2016-08-15 Thread Apache Jenkins Server 
The Apache Jenkins build system has built Camel.trunk.notest (build #2843)

Status: Still Failing

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

Camel.2.17.x.notest - Build # 107 - Failure

2016-08-15 Thread Apache Jenkins Server 
The Apache Jenkins build system has built Camel.2.17.x.notest (build #107)

Status: Failure

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

Re: [RESULT] [VOTE] Camel 2.17.3

2016-08-15 Thread Claus Ibsen 
On Thu, Aug 11, 2016 at 6:21 PM, Daniel Kulp  wrote:
>
> Claus,
>
> Thanks…
>
> I think there are other steps I haven’t had time to finish (updating schemas 
> and such).   Did you handle those as well or do I need to circle back on it?
>

No I didn't upload any schemas etc. as that likely needs to be done
from the build that was done for the release. However we could likely
find the XSD scheams from the 2.17.3 binaries and upload them manually
if they are no longer on your laptop.

I wonder if there isn't something we can do to make the release
producer smarter and more automated. Can we have some scripts that can
download from the JARs a release and then upload the needed schemas
and javadoc etc.

Then we can do that as a post install procedure after the artifacts
has been promoted to maven central.
And then we could use a CI server to do the regular release.


The steps I did was 14, 15, 16 and 17 from this page:
http://camel.apache.org/release-guide.html
And I did 18 last weekend ;)





> Dan
>
>
>> On Aug 11, 2016, at 11:02 AM, Claus Ibsen  wrote:
>>
>> Hi
>>
>> Just to close this I did the announcement.
>>
>> Thanks Dan for cutting the release.
>>
>>
>>
>> On Wed, Aug 10, 2016 at 8:25 AM, Claus Ibsen  wrote:
>>> Hi
>>>
>>> I dont think we have announced this released yet. Can we have that done.
>>>
>>>
>>>
>>> On Mon, Aug 8, 2016 at 3:33 PM, Daniel Kulp  wrote:
 We have 9 +1 votes and no other votes.   This vote passes..

 Dan



> On Aug 4, 2016, at 4:20 PM, Daniel Kulp  wrote:
>
>
> This is a vote to release Camel 2.17.3
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1052/ 
> 
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ad245911cc8db1a8c57ec7825f7fd630f2a4ec58
>  
> 
>
>
>
> Here is my +1
>
> --
> Daniel Kulp
> dk...@apache.org  - http://dankulp.com/blog 
> 
> Talend Community Coder - http://coders.talend.com 
> 

 --
 Daniel Kulp
 dk...@apache.org  - http://dankulp.com/blog 
 
 Talend Community Coder - http://coders.talend.com 
 
>>>
>>>
>>>
>>> --
>>> 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
>
> --
> Daniel Kulp
> dk...@apache.org  - http://dankulp.com/blog 
> 
> Talend Community Coder - http://coders.talend.com 



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

[GitHub] camel pull request #1124: CAMEL-10245 JPA detached entity fix

2016-08-15 Thread bgaudaen 
GitHub user bgaudaen opened a pull request:

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

CAMEL-10245 JPA detached entity fix

Fixed JpaProducer when removing an entity that is not attached to current 
persistence context

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

$ git pull https://github.com/bgaudaen/camel jpa-detached-entity-fix

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

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


commit 10d5186f5e8a56371bad98307623f85c42273d35
Author: Bob Gaudaen 
Date:   2016-08-15T14:25:04Z

CAMEL-10245 Updated JpaProducerRemoveTest to remove previously persisted 
entity instead of new entity

commit f8e5bba6faa0b644867752564a28e5bf8f5f4c81
Author: Bob Gaudaen 
Date:   2016-08-15T14:31:30Z

CAMEL-10245 Fixed JpaProducer remove feature

Check if entity is managed in current persistence context and merge if 
needed before removing.




---
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 #1118: Fix for CAMEL-8287

2016-08-15 Thread hutchkintoot 
Github user hutchkintoot closed the pull request at:

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


---
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 #1123: Fix for CAMEL-8287

2016-08-15 Thread hutchkintoot 
GitHub user hutchkintoot opened a pull request:

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

Fix for CAMEL-8287

Allows a user to supply a custom URIResolver to be used to resolve imports 
in his/her schematron rules files.

Fix now applied to master. But we would really need to have this back 
ported to the 2.16.x and 2.17.x branches if possible. 

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

$ git pull https://github.com/hutchkintoot/camel CAMEL-8287-master

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

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


commit ffb4b1cd22f27767f320fcec5de13dd6aec27916
Author: Johan Mörén 
Date:   2016-08-15T13:14:27Z

Fix for CAMEL-8287

Allows a user to supply a custom URIResolver to be used to resolve imports 
in his/her schematron rules files.




---
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 #1122: CAMEL-10171 memory leak when continuation expires

2016-08-15 Thread onders86 
Github user onders86 closed the pull request at:

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


---
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 #1120: CAMEL-10244: Make connection establishment fuly as...

2016-08-15 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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 #1117: CAMEL-10222: New spring-boot starters

2016-08-15 Thread asfgit 
Github user asfgit closed the pull request at:

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


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