On Tue, Jul 30, 2013 at 11:46 AM, Bilgin Ibryam 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
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
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 co
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 | ht
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 compo
