[GitHub] camel pull request #1921: CAMEL-11760: camel-itest-karaf - CamelServicenowTe...

[tadayosi]

GitHub user tadayosi opened a pull request:

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

CAMEL-11760: camel-itest-karaf - CamelServicenowTest fails

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

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

$ git pull https://github.com/tadayosi/camel CAMEL-11760

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

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


commit b151b44c5f4af3b6044b23a3d5acd2dd71a885d1
Author: Tadayoshi Sato 
Date:   2017-09-07T04:06:17Z

CAMEL-11760: camel-itest-karaf - CamelServicenowTest fails




---

[GitHub] camel pull request #1920: CAMEL-11759: camel-itest-karaf - CamelNagiosTest f...

[tadayosi]

GitHub user tadayosi opened a pull request:

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

CAMEL-11759: camel-itest-karaf - CamelNagiosTest fails

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

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

$ git pull https://github.com/tadayosi/camel CAMEL-11759

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

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


commit 689d72a9aa8391be686713853c2c63f499413458
Author: Tadayoshi Sato 
Date:   2017-09-07T03:10:00Z

CAMEL-11759: camel-itest-karaf - CamelNagiosTest fails




---

[GitHub] camel pull request #1919: CAMEL-11726: Fixed the Elsql producer inconsistent...

[bonbonmark]

GitHub user bonbonmark opened a pull request:

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

CAMEL-11726: Fixed the Elsql producer inconsistent behavior compared …

Add unit test to ensure we can get header value at following step

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

$ git pull https://github.com/bonbonmark/camel CAMEL-11726

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

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


commit 445771214b31f3f436ab567f1deb7d2bf97d6c71
Author: Mark You 
Date:   2017-09-07T03:08:37Z

CAMEL-11726: Fixed the Elsql producer inconsistent behavior compared , add 
test case to ensure we can get header value




---

Re: CamelBeanValidatorTest is failing

[Tadayoshi Sato]

Hi Andrea,

Yeah, it doesn't reproduce locally in my laptop, either.

The last commit that the camel-itest-karaf ran successfully on Jenkins was
this on Aug 1:
https://github.com/apache/camel/commit/0b243a48aea3f30fba8460c7b26f7b184b3c6456
so it could be that any changes that were committed right after the commit
may have caused the itest failures. (It's also possible that any external
factors such as changes on the maven central repo that happened right after
Aug 1  could have caused it though.)

However the original failed build history #2210 is already gone on Jenkins:
https://builds.apache.org/job/Camel.trunk.itest.karaf/
so it's hard to detect which one is the culprit.

I found this ticket. Was this itest failure the original motivation for the
task?
https://issues.apache.org/jira/browse/CAMEL-11650


On Thu, Sep 7, 2017 at 10:24 AM, Tadayoshi Sato 
wrote:

> Filed the JIRA: https://issues.apache.org/jira/browse/CAMEL-11758
> I'll look into it.
>
> On Wed, Sep 6, 2017 at 3:02 PM, Andrea Cosentino 
> wrote:
>
>> Tested locally it seems to work.
>>
>> [org.ops4j.store.intern.TemporaryStore] : Exit store():
>> 8e7251cf3141ec0862eb074f2466f6df6820a6d0
>> [org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : Preparing and
>> Installing bundle (from stream )..
>> [org.ops4j.pax.exam.rbc.client.RemoteBundleContextClient] : Packing
>> probe into memory for true RMI. Hopefully things will fill in..
>> [org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : Installed bundle
>> (from stream) as ID: 80
>> [org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : call
>> [[TestAddress:PaxExam-d99f7da4-022e-4e50-8778-4ec519603761
>> root:PaxExam-5408707c-548d-485f-b49e-98d07bdbbdfc]]
>> [org.ops4j.pax.exam.karaf.container.internal.KarafTestContainer] :
>> Shutting down the test container (Pax Runner)
>> [org.ops4j.pax.exam.spi.reactors.ReactorManager] : suite finished
>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.461
>> sec - in org.apache.camel.itest.karaf.CamelBeanValidatorTest
>>
>>
>>
>> --
>> Andrea Cosentino
>> --
>> Apache Camel PMC Member
>> Apache Karaf Committer
>> Apache Servicemix PMC Member
>> Email: ancosen1...@yahoo.com
>> Twitter: @oscerd2
>> Github: oscerd
>>
>>
>>
>>
>>
>>
>>
>> On Wednesday, September 6, 2017, 6:43:22 AM GMT+2, Tadayoshi Sato <
>> sato.tadayo...@gmail.com> wrote:
>>
>>
>>
>>
>>
>> Looks like CamelBeanValidatorTest in camel-itest-karaf is failing:
>>
>> https://builds.apache.org/job/Camel.trunk.itest.karaf/2397/console
>>
>>
>> Tests in error:
>>   CamelBeanValidatorTest.test » WrappedTestContainer
>> [test(org.apache.camel.ites...
>>
>>
>> Best regards,
>> Tadayoshi
>>
>>
>

Re: CamelBeanValidatorTest is failing

[Tadayoshi Sato]

Filed the JIRA: https://issues.apache.org/jira/browse/CAMEL-11758
I'll look into it.

On Wed, Sep 6, 2017 at 3:02 PM, Andrea Cosentino 
wrote:

> Tested locally it seems to work.
>
> [org.ops4j.store.intern.TemporaryStore] : Exit store():
> 8e7251cf3141ec0862eb074f2466f6df6820a6d0
> [org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : Preparing and
> Installing bundle (from stream )..
> [org.ops4j.pax.exam.rbc.client.RemoteBundleContextClient] : Packing probe
> into memory for true RMI. Hopefully things will fill in..
> [org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : Installed bundle
> (from stream) as ID: 80
> [org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : call
> [[TestAddress:PaxExam-d99f7da4-022e-4e50-8778-4ec519603761
> root:PaxExam-5408707c-548d-485f-b49e-98d07bdbbdfc]]
> [org.ops4j.pax.exam.karaf.container.internal.KarafTestContainer] :
> Shutting down the test container (Pax Runner)
> [org.ops4j.pax.exam.spi.reactors.ReactorManager] : suite finished
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.461 sec
> - in org.apache.camel.itest.karaf.CamelBeanValidatorTest
>
>
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
>
> On Wednesday, September 6, 2017, 6:43:22 AM GMT+2, Tadayoshi Sato <
> sato.tadayo...@gmail.com> wrote:
>
>
>
>
>
> Looks like CamelBeanValidatorTest in camel-itest-karaf is failing:
>
> https://builds.apache.org/job/Camel.trunk.itest.karaf/2397/console
>
>
> Tests in error:
>   CamelBeanValidatorTest.test » WrappedTestContainer
> [test(org.apache.camel.ites...
>
>
> Best regards,
> Tadayoshi
>
>

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

[Apache Jenkins Server]

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

Status: Still Failing

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

Re: Nabble forums

[Pontus Ullgren]

Sorry my bad. Must have had a old version cached somehow.
The link is indeed no longer there.


// Pontus

On Wed, 6 Sep 2017 at 22:14 Pontus Ullgren  wrote:

> Actually there is a link to this page from the Camle website in the menu
> on the right hand side.
>
> In the section Community there is a link "Discussion Forums". That page
> still mentions and links to Nabble.
>
> // Pontus
>
> On Wed, 6 Sep 2017 at 10:04 Claus Ibsen  wrote:
>
>> On Wed, Sep 6, 2017 at 9:57 AM, Guillaume Nodet 
>> wrote:
>> > I think that's a good move, however it hasn't been followed through yet:
>> >   http://camel.apache.org/discussion-forums.html
>> >
>>
>> Ah that is the old page, there is no link to that from the Camel
>> website, eg the front page, on that menu on the right hand side.
>>
>> We can try to delete that page in wiki, but AFAIK its not deleted as
>> .html file.
>> But an alternative is to edit that wiki page and remove all that nabble
>> stuff.
>>
>>
>> > 2017-09-06 9:46 GMT+02:00 Claus Ibsen :
>> >
>> >> Hi Guillaume
>> >>
>> >> The PMC have discussed this a while back and we are dropping Nabble,
>> >> eg your first bullet.
>> >> We have removed any links or mentions of Nabble on the Camel website.
>> >>
>> >> Thanks for making it a read-only. Also we have alot of stuff to do
>> >> already so I dont think we want/need more to administrate etc.
>> >>
>> >> And today there are better alternatives than nabble, either the real
>> >> mailing list, or using stackoverflow or gitter etc.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On Wed, Sep 6, 2017 at 9:40 AM, Guillaume Nodet 
>> wrote:
>> >> > Last week, I spent a few hours removing a lot of spams from the
>> nabble
>> >> > forums.
>> >> > In order to not be spammed anymore, I disabled the creation and
>> reply to
>> >> > the forums, thereby acting as a read-only archive of the mailing
>> lists.
>> >> > I'm getting requests from users to be able to post.
>> >> >
>> >> > I think we can:
>> >> >   * leave it as is and force users to use the mailing lists
>> >> >   * create a team and put users in that team so that they can write
>> in
>> >> the
>> >> > forums (i think this has to be done manually after a request from the
>> >> user)
>> >> >   * revert and allow anyone to write (which will bring spam again)
>> >> >
>> >> > What you guys want to do ?
>> >> > In all cases, it would be nice if some additional PMC members could
>> step
>> >> in
>> >> > to administrate the nabble forums.
>> >> >
>> >> > Cheers,
>> >> > Guillaume Nodet
>> >>
>> >>
>> >>
>> >> --
>> >> Claus Ibsen
>> >> -
>> >> http://davsclaus.com @davsclaus
>> >> Camel in Action 2: https://www.manning.com/ibsen2
>> >>
>> >
>> >
>> >
>> > --
>> > 
>> > Guillaume Nodet
>>
>>
>>
>> --
>> Claus Ibsen
>> -
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>

Re: Nabble forums

[Pontus Ullgren]

Actually there is a link to this page from the Camle website in the menu on
the right hand side.

In the section Community there is a link "Discussion Forums". That page
still mentions and links to Nabble.

// Pontus

On Wed, 6 Sep 2017 at 10:04 Claus Ibsen  wrote:

> On Wed, Sep 6, 2017 at 9:57 AM, Guillaume Nodet  wrote:
> > I think that's a good move, however it hasn't been followed through yet:
> >   http://camel.apache.org/discussion-forums.html
> >
>
> Ah that is the old page, there is no link to that from the Camel
> website, eg the front page, on that menu on the right hand side.
>
> We can try to delete that page in wiki, but AFAIK its not deleted as .html
> file.
> But an alternative is to edit that wiki page and remove all that nabble
> stuff.
>
>
> > 2017-09-06 9:46 GMT+02:00 Claus Ibsen :
> >
> >> Hi Guillaume
> >>
> >> The PMC have discussed this a while back and we are dropping Nabble,
> >> eg your first bullet.
> >> We have removed any links or mentions of Nabble on the Camel website.
> >>
> >> Thanks for making it a read-only. Also we have alot of stuff to do
> >> already so I dont think we want/need more to administrate etc.
> >>
> >> And today there are better alternatives than nabble, either the real
> >> mailing list, or using stackoverflow or gitter etc.
> >>
> >>
> >>
> >>
> >>
> >> On Wed, Sep 6, 2017 at 9:40 AM, Guillaume Nodet 
> wrote:
> >> > Last week, I spent a few hours removing a lot of spams from the nabble
> >> > forums.
> >> > In order to not be spammed anymore, I disabled the creation and reply
> to
> >> > the forums, thereby acting as a read-only archive of the mailing
> lists.
> >> > I'm getting requests from users to be able to post.
> >> >
> >> > I think we can:
> >> >   * leave it as is and force users to use the mailing lists
> >> >   * create a team and put users in that team so that they can write in
> >> the
> >> > forums (i think this has to be done manually after a request from the
> >> user)
> >> >   * revert and allow anyone to write (which will bring spam again)
> >> >
> >> > What you guys want to do ?
> >> > In all cases, it would be nice if some additional PMC members could
> step
> >> in
> >> > to administrate the nabble forums.
> >> >
> >> > Cheers,
> >> > Guillaume Nodet
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -
> >> http://davsclaus.com @davsclaus
> >> Camel in Action 2: https://www.manning.com/ibsen2
> >>
> >
> >
> >
> > --
> > 
> > Guillaume Nodet
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

[GitHub] camel pull request #1917: CAMEL-11726: Fixed the Elsql producer inconsistent...

[aldettinger]

Github user aldettinger closed the pull request at:

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


---

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

[Apache Jenkins Server]

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

Status: Still Failing

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

Re: Re: Apache Camel 2.19.3 Release

[Claus Ibsen]

Hi Gregor

That sounds good.

We are working on getting the bits ready for 2.20.0 release as well. I
think we should try to aim for a release at the end of this month.

We should post a new post on @dev about the 2.20.0 release, so we keep
the 2.19.x and 2.20.0 talks separated.

On Wed, Sep 6, 2017 at 5:19 PM, Gregor Zurowski
 wrote:
> Yes, I can cut the 2.19.3 release this weekend.
>
> When are we ready for 2.20.0?
>
> Thanks,
> Gregor
>
>
> On Wed, Sep 6, 2017 at 5:13 PM, Andrea Cosentino
>  wrote:
>> Gregor, do you think you can take care of this release?
>> Thanks
>>
>>   Il mer, 6 set, 2017 alle 15:50, Claus Ibsen ha 
>> scritto:   +1
>>
>> I will create a 2.19.4 version so if we wont get time to fix all the
>> remainder 2.19.3 tickets we can move them to the next.
>>
>> On Wed, Sep 6, 2017 at 2:58 PM, Andrea Cosentino
>>  wrote:
>>> Hi all,
>>>
>>> I guess we can think about releasing a patch release for 2.19.3. From 
>>> 2.19.2 about one month has passed. I guess we need to release a bit more 
>>> frequently.
>>>
>>> So maybe it would be good to release this patch by the end of this month, 
>>> maybe with 2.20.0
>>>
>>> What do you think guys?
>>>
>>> Thanks.
>>>
>>> --
>>> Andrea Cosentino
>>> --
>>> Apache Camel PMC Member
>>> Apache Karaf Committer
>>> Apache Servicemix PMC Member
>>> Email: ancosen1...@yahoo.com
>>> Twitter: @oscerd2
>>> Github: oscerd
>>
>>
>>
>> --
>> 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

[GitHub] camel pull request #1918: CAMEL-11757: Upgraded CometD library

[vrlgohel]

GitHub user vrlgohel opened a pull request:

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

CAMEL-11757: Upgraded CometD library

Fix for issue: https://issues.apache.org/jira/browse/CAMEL-11757

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

$ git pull https://github.com/vrlgohel/camel-1 CAMEL-11757

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

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


commit 2c092cbc1fe83d6a5257ddc386688279eb61ccfb
Author: Viral Gohel 
Date:   2017-09-06T17:28:48Z

CAMEL-11757: Upgraded CometD library




---

Re: Re: Apache Camel 2.19.3 Release

[Gregor Zurowski]

Yes, I can cut the 2.19.3 release this weekend.

When are we ready for 2.20.0?

Thanks,
Gregor


On Wed, Sep 6, 2017 at 5:13 PM, Andrea Cosentino
 wrote:
> Gregor, do you think you can take care of this release?
> Thanks
>
>   Il mer, 6 set, 2017 alle 15:50, Claus Ibsen ha 
> scritto:   +1
>
> I will create a 2.19.4 version so if we wont get time to fix all the
> remainder 2.19.3 tickets we can move them to the next.
>
> On Wed, Sep 6, 2017 at 2:58 PM, Andrea Cosentino
>  wrote:
>> Hi all,
>>
>> I guess we can think about releasing a patch release for 2.19.3. From 2.19.2 
>> about one month has passed. I guess we need to release a bit more frequently.
>>
>> So maybe it would be good to release this patch by the end of this month, 
>> maybe with 2.20.0
>>
>> What do you think guys?
>>
>> Thanks.
>>
>> --
>> Andrea Cosentino
>> --
>> Apache Camel PMC Member
>> Apache Karaf Committer
>> Apache Servicemix PMC Member
>> Email: ancosen1...@yahoo.com
>> Twitter: @oscerd2
>> Github: oscerd
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

[GitHub] camel pull request #1917: CAMEL-11726: Fixed the Elsql producer inconsistent...

[aldettinger]

GitHub user aldettinger opened a pull request:

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

CAMEL-11726: Fixed the Elsql producer inconsistent behavior

Fixed the Elsql producer inconsistent behavior compared to sql component 
producer.

[CAMEL-11726](https://issues.apache.org/jira/browse/CAMEL-11726) has more.

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

$ git pull https://github.com/aldettinger/camel master

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

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


commit b23e8dc25b7d3d6a281b8404337c21fca1b643ae
Author: aldettinger 
Date:   2017-09-06T15:13:47Z

CAMEL-11726: Fixed the Elsql producer inconsistent behavior compared to sql 
component producer




---

R: Re: Apache Camel 2.19.3 Release

[Andrea Cosentino]

Gregor, do you think you can take care of this release?
Thanks 
 
  Il mer, 6 set, 2017 alle 15:50, Claus Ibsen ha 
scritto:   +1

I will create a 2.19.4 version so if we wont get time to fix all the
remainder 2.19.3 tickets we can move them to the next.

On Wed, Sep 6, 2017 at 2:58 PM, Andrea Cosentino
 wrote:
> Hi all,
>
> I guess we can think about releasing a patch release for 2.19.3. From 2.19.2 
> about one month has passed. I guess we need to release a bit more frequently.
>
> So maybe it would be good to release this patch by the end of this month, 
> maybe with 2.20.0
>
> What do you think guys?
>
> Thanks.
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd



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

Camel.2.18.x.notest - Build # 183 - Still Failing

[Apache Jenkins Server]

The Apache Jenkins build system has built Camel.2.18.x.notest (build #183)

Status: Still Failing

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

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

[Apache Jenkins Server]

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

Status: Still Failing

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

Re: Apache Camel 2.19.3 Release

[Claus Ibsen]

+1

I will create a 2.19.4 version so if we wont get time to fix all the
remainder 2.19.3 tickets we can move them to the next.

On Wed, Sep 6, 2017 at 2:58 PM, Andrea Cosentino
 wrote:
> Hi all,
>
> I guess we can think about releasing a patch release for 2.19.3. From 2.19.2 
> about one month has passed. I guess we need to release a bit more frequently.
>
> So maybe it would be good to release this patch by the end of this month, 
> maybe with 2.20.0
>
> What do you think guys?
>
> Thanks.
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd



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

Apache Camel 2.19.3 Release

[Andrea Cosentino]

Hi all,

I guess we can think about releasing a patch release for 2.19.3. From 2.19.2 
about one month has passed. I guess we need to release a bit more frequently.

So maybe it would be good to release this patch by the end of this month, maybe 
with 2.20.0

What do you think guys?

Thanks.

--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd

[GitHub] camel pull request #1869: Camel_SalesForce: Give possibility to update Owner...

[Sw1m1k]

Github user Sw1m1k closed the pull request at:

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


---

[GitHub] camel pull request #1916: Camel 2.19.x

[asfgit]

Github user asfgit closed the pull request at:

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


---

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

[Apache Jenkins Server]

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

Status: Still Failing

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

Camel.2.18.x.notest - Build # 182 - Still Failing

[Apache Jenkins Server]

The Apache Jenkins build system has built Camel.2.18.x.notest (build #182)

Status: Still Failing

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

Camel.2.18.x.notest - Build # 181 - Still Failing

[Apache Jenkins Server]

The Apache Jenkins build system has built Camel.2.18.x.notest (build #181)

Status: Still Failing

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

Re: Nabble forums

[Claus Ibsen]

On Wed, Sep 6, 2017 at 9:57 AM, Guillaume Nodet  wrote:
> I think that's a good move, however it hasn't been followed through yet:
>   http://camel.apache.org/discussion-forums.html
>

Ah that is the old page, there is no link to that from the Camel
website, eg the front page, on that menu on the right hand side.

We can try to delete that page in wiki, but AFAIK its not deleted as .html file.
But an alternative is to edit that wiki page and remove all that nabble stuff.


> 2017-09-06 9:46 GMT+02:00 Claus Ibsen :
>
>> Hi Guillaume
>>
>> The PMC have discussed this a while back and we are dropping Nabble,
>> eg your first bullet.
>> We have removed any links or mentions of Nabble on the Camel website.
>>
>> Thanks for making it a read-only. Also we have alot of stuff to do
>> already so I dont think we want/need more to administrate etc.
>>
>> And today there are better alternatives than nabble, either the real
>> mailing list, or using stackoverflow or gitter etc.
>>
>>
>>
>>
>>
>> On Wed, Sep 6, 2017 at 9:40 AM, Guillaume Nodet  wrote:
>> > Last week, I spent a few hours removing a lot of spams from the nabble
>> > forums.
>> > In order to not be spammed anymore, I disabled the creation and reply to
>> > the forums, thereby acting as a read-only archive of the mailing lists.
>> > I'm getting requests from users to be able to post.
>> >
>> > I think we can:
>> >   * leave it as is and force users to use the mailing lists
>> >   * create a team and put users in that team so that they can write in
>> the
>> > forums (i think this has to be done manually after a request from the
>> user)
>> >   * revert and allow anyone to write (which will bring spam again)
>> >
>> > What you guys want to do ?
>> > In all cases, it would be nice if some additional PMC members could step
>> in
>> > to administrate the nabble forums.
>> >
>> > Cheers,
>> > Guillaume Nodet
>>
>>
>>
>> --
>> Claus Ibsen
>> -
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>>
>
>
>
> --
> 
> Guillaume Nodet



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

Re: Nabble forums

[Guillaume Nodet]

I think that's a good move, however it hasn't been followed through yet:
  http://camel.apache.org/discussion-forums.html

2017-09-06 9:46 GMT+02:00 Claus Ibsen :

> Hi Guillaume
>
> The PMC have discussed this a while back and we are dropping Nabble,
> eg your first bullet.
> We have removed any links or mentions of Nabble on the Camel website.
>
> Thanks for making it a read-only. Also we have alot of stuff to do
> already so I dont think we want/need more to administrate etc.
>
> And today there are better alternatives than nabble, either the real
> mailing list, or using stackoverflow or gitter etc.
>
>
>
>
>
> On Wed, Sep 6, 2017 at 9:40 AM, Guillaume Nodet  wrote:
> > Last week, I spent a few hours removing a lot of spams from the nabble
> > forums.
> > In order to not be spammed anymore, I disabled the creation and reply to
> > the forums, thereby acting as a read-only archive of the mailing lists.
> > I'm getting requests from users to be able to post.
> >
> > I think we can:
> >   * leave it as is and force users to use the mailing lists
> >   * create a team and put users in that team so that they can write in
> the
> > forums (i think this has to be done manually after a request from the
> user)
> >   * revert and allow anyone to write (which will bring spam again)
> >
> > What you guys want to do ?
> > In all cases, it would be nice if some additional PMC members could step
> in
> > to administrate the nabble forums.
> >
> > Cheers,
> > Guillaume Nodet
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>



-- 

Guillaume Nodet

Re: Nabble forums

[Claus Ibsen]

Hi Guillaume

The PMC have discussed this a while back and we are dropping Nabble,
eg your first bullet.
We have removed any links or mentions of Nabble on the Camel website.

Thanks for making it a read-only. Also we have alot of stuff to do
already so I dont think we want/need more to administrate etc.

And today there are better alternatives than nabble, either the real
mailing list, or using stackoverflow or gitter etc.





On Wed, Sep 6, 2017 at 9:40 AM, Guillaume Nodet  wrote:
> Last week, I spent a few hours removing a lot of spams from the nabble
> forums.
> In order to not be spammed anymore, I disabled the creation and reply to
> the forums, thereby acting as a read-only archive of the mailing lists.
> I'm getting requests from users to be able to post.
>
> I think we can:
>   * leave it as is and force users to use the mailing lists
>   * create a team and put users in that team so that they can write in the
> forums (i think this has to be done manually after a request from the user)
>   * revert and allow anyone to write (which will bring spam again)
>
> What you guys want to do ?
> In all cases, it would be nice if some additional PMC members could step in
> to administrate the nabble forums.
>
> Cheers,
> Guillaume Nodet



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

Fwd: Nabble forums

[Guillaume Nodet]

Last week, I spent a few hours removing a lot of spams from the nabble
forums.
In order to not be spammed anymore, I disabled the creation and reply to
the forums, thereby acting as a read-only archive of the mailing lists.
I'm getting requests from users to be able to post.

I think we can:
  * leave it as is and force users to use the mailing lists
  * create a team and put users in that team so that they can write in the
forums (i think this has to be done manually after a request from the user)
  * revert and allow anyone to write (which will bring spam again)

What you guys want to do ?
In all cases, it would be nice if some additional PMC members could step in
to administrate the nabble forums.

Cheers,
Guillaume Nodet

[GitHub] camel pull request #1915: CAMEL-11732: Add or update READMEs to itests

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: CamelBeanValidatorTest is failing

[Andrea Cosentino]

Tested locally it seems to work.
[org.ops4j.store.intern.TemporaryStore] : Exit store(): 
8e7251cf3141ec0862eb074f2466f6df6820a6d0[org.ops4j.pax.exam.container.remote.RBCRemoteTarget]
 : Preparing and Installing bundle (from stream )..
[org.ops4j.pax.exam.rbc.client.RemoteBundleContextClient] : Packing probe into 
memory for true RMI. Hopefully things will fill in..
[org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : Installed bundle (from 
stream) as ID: 80
[org.ops4j.pax.exam.container.remote.RBCRemoteTarget] : call 
[[TestAddress:PaxExam-d99f7da4-022e-4e50-8778-4ec519603761 
root:PaxExam-5408707c-548d-485f-b49e-98d07bdbbdfc]]
[org.ops4j.pax.exam.karaf.container.internal.KarafTestContainer] : Shutting 
down the test container (Pax Runner)
[org.ops4j.pax.exam.spi.reactors.ReactorManager] : suite finished
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.461 sec - in 
org.apache.camel.itest.karaf.CamelBeanValidatorTest



--
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd




 
 
 On Wednesday, September 6, 2017, 6:43:22 AM GMT+2, Tadayoshi Sato 
 wrote: 





Looks like CamelBeanValidatorTest in camel-itest-karaf is failing:

https://builds.apache.org/job/Camel.trunk.itest.karaf/2397/console


Tests in error:
  CamelBeanValidatorTest.test » WrappedTestContainer
[test(org.apache.camel.ites...


Best regards,
Tadayoshi