You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Bilgin Ibryam <bi...@gmail.com> on 2013/07/23 19:53:15 UTC

Infinispan component questions

Hi guys,

I've created a JBoss Infinispan component for Camel
It is here https://github.com/bibryam/camel-infinispan

I've updated it to use version 6.0.0.Alpha1 which is reliesed under ASL2

Do we have any policy for not adding libraries which are Alpha, when
would be a good time to add this component to Camel trunk?

Cheers
Bilgin

Re: Infinispan component questions

Posted by Claus Ibsen <cl...@gmail.com>.
On Tue, Jul 30, 2013 at 11:46 AM, Bilgin Ibryam <bi...@gmail.com> wrote:
> Thanks for the suggestions.
>
> @Claus are you suggesting to wait till a GA release is available or
> add the component to master now and not release it till there is GA
> release of Infinispan?
>

The code can be added to master now. We can just wait to include
camel-infinispan in the official releases until Infinispan has a GA
release.

Having the code in master allows us to test it with the CI servers and
also work on getting it working with OSGi etc. And if there is some
glitches we can report that back to the infinispan team, so they can
possible fix it before a GA release.



> Thanks
> Bilgin
>
>
>> As its alpha release it may have API changes on the way and whatnot.
>> So I think we should wait until its first GA release.
>>
>> Though the code can be committed to master at ASF as we can just avoid
>> release camel-infinispan. But having the code at ASF allows us to work
>> on it, and as well test it with OSGi / Karaf etc.
>>
>> On Wed, Jul 24, 2013 at 11:01 AM, Willem jiang <wi...@gmail.com> wrote:
>>> I think we can wait for the Infinispan RC release before movie the component into Camel trunk.
>>> In this way, camel-infinispan component will not hold the release steps of Camel.
>>>
>>> Any thoughts?
>>>
>>> --
>>> Willem Jiang
>>>
>>> Red Hat, Inc.
>>> FuseSource is now part of Red Hat
>>> Web: http://www.fusesource.com | http://www.redhat.com
>>> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
>>>           http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
>>> Twitter: willemjiang
>>> Weibo: 姜宁willem
>>>
>>>
>>>
>>>
>>>
>>> On Wednesday, July 24, 2013 at 1:53 AM, Bilgin Ibryam wrote:
>>>
>>>> Hi guys,
>>>>
>>>> I've created a JBoss Infinispan component for Camel
>>>> It is here https://github.com/bibryam/camel-infinispan
>>>>
>>>> I've updated it to use version 6.0.0.Alpha1 which is reliesed under ASL2
>>>>
>>>> Do we have any policy for not adding libraries which are Alpha, when
>>>> would be a good time to add this component to Camel trunk?
>>>>
>>>> Cheers
>>>> Bilgin
>>>
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> Email: cibsen@redhat.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: Infinispan component questions

Posted by Bilgin Ibryam <bi...@gmail.com>.
Thanks for the suggestions.

@Claus are you suggesting to wait till a GA release is available or
add the component to master now and not release it till there is GA
release of Infinispan?

Thanks
Bilgin


> As its alpha release it may have API changes on the way and whatnot.
> So I think we should wait until its first GA release.
>
> Though the code can be committed to master at ASF as we can just avoid
> release camel-infinispan. But having the code at ASF allows us to work
> on it, and as well test it with OSGi / Karaf etc.
>
> On Wed, Jul 24, 2013 at 11:01 AM, Willem jiang <wi...@gmail.com> wrote:
>> I think we can wait for the Infinispan RC release before movie the component into Camel trunk.
>> In this way, camel-infinispan component will not hold the release steps of Camel.
>>
>> Any thoughts?
>>
>> --
>> Willem Jiang
>>
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Web: http://www.fusesource.com | http://www.redhat.com
>> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
>>           http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>>
>>
>>
>>
>> On Wednesday, July 24, 2013 at 1:53 AM, Bilgin Ibryam wrote:
>>
>>> Hi guys,
>>>
>>> I've created a JBoss Infinispan component for Camel
>>> It is here https://github.com/bibryam/camel-infinispan
>>>
>>> I've updated it to use version 6.0.0.Alpha1 which is reliesed under ASL2
>>>
>>> Do we have any policy for not adding libraries which are Alpha, when
>>> would be a good time to add this component to Camel trunk?
>>>
>>> Cheers
>>> Bilgin
>>
>>
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen

Re: Infinispan component questions

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Well yeah we should go for the 6.0 release as thats ASL 2.0 licensed.
We should work with the inifinispan team to ensure it works in OSGi
also (if possible).
As its alpha release it may have API changes on the way and whatnot.
So I think we should wait until its first GA release.

Though the code can be committed to master at ASF as we can just avoid
release camel-infinispan. But having the code at ASF allows us to work
on it, and as well test it with OSGi / Karaf etc.

On Wed, Jul 24, 2013 at 11:01 AM, Willem jiang <wi...@gmail.com> wrote:
> I think we can wait for the Infinispan RC release before movie the component into Camel trunk.
> In this way, camel-infinispan component will not hold the release steps of Camel.
>
> Any thoughts?
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Web: http://www.fusesource.com | http://www.redhat.com
> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
>           http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
>
>
> On Wednesday, July 24, 2013 at 1:53 AM, Bilgin Ibryam wrote:
>
>> Hi guys,
>>
>> I've created a JBoss Infinispan component for Camel
>> It is here https://github.com/bibryam/camel-infinispan
>>
>> I've updated it to use version 6.0.0.Alpha1 which is reliesed under ASL2
>>
>> Do we have any policy for not adding libraries which are Alpha, when
>> would be a good time to add this component to Camel trunk?
>>
>> Cheers
>> Bilgin
>
>
>



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: Infinispan component questions

Posted by Willem jiang <wi...@gmail.com>.
I think we can wait for the Infinispan RC release before movie the component into Camel trunk.
In this way, camel-infinispan component will not hold the release steps of Camel.

Any thoughts?  

--  
Willem Jiang

Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
          http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem





On Wednesday, July 24, 2013 at 1:53 AM, Bilgin Ibryam wrote:

> Hi guys,
>  
> I've created a JBoss Infinispan component for Camel
> It is here https://github.com/bibryam/camel-infinispan
>  
> I've updated it to use version 6.0.0.Alpha1 which is reliesed under ASL2
>  
> Do we have any policy for not adding libraries which are Alpha, when
> would be a good time to add this component to Camel trunk?
>  
> Cheers
> Bilgin