On Mon, Mar 5, 2012 at 12:47 PM, Deependra Ariyadewa d...@wso2.com wrote:
On Mon, Mar 5, 2012 at 12:33 PM, Rajika Kumarasiri raj...@wso2.comwrote:
It seems the Cassandra version that you are using tightly couple into the
an older version of the thrift. In that case we will have to maintain
Are we not using OSGi for these dependencies? Its meant to solve these sort
of problems!
Paul
On 5 March 2012 07:17, Deependra Ariyadewa d...@wso2.com wrote:
On Mon, Mar 5, 2012 at 12:33 PM, Rajika Kumarasiri raj...@wso2.comwrote:
It seems the Cassandra version that you are using tightly
Yes, it means that people have not specified the correct package import
export versions. The different versions of these OSGi bundles can coexist.
Can we fix these import-export versions at least for these bundles?
On Mon, Mar 5, 2012 at 3:10 PM, Paul Fremantle p...@wso2.com wrote:
Are we not
Asela, could you check whether you can fix the problem without removing the
jar?
We will have to maintain two versions if two components have version
specific dependencies...
On Mon, Mar 5, 2012 at 3:23 PM, Afkham Azeez az...@wso2.com wrote:
Yes, it means that people have not specified the
On Mon, Mar 5, 2012 at 3:56 PM, Tharindu Mathew thari...@wso2.com wrote:
Asela, could you check whether you can fix the problem without removing
the jar?
We will have to maintain two versions if two components have version
specific dependencies...
Yes will look. As Azeez mentioned, There
Hi All,
I need to upgrade following dependencies in Carbon trunk to support
Cassandra 1.x.x.
concurrentlinkedhashmap-lru version 1.1 to 1.2
high-scale-lib version 1.0 to 1.1.2
antlr version 2.7.7 to 3.2
Also I need to add following dependency to trunk.
jamm version 0.2.5
There is a dependency
There is a dependency mismatch when I try to start Cassandra in Carbon
core with libthrift 0.8.0 ( carbon trunk libthrift version) but it works
fine with libthrift 0.6.1. Please advice me how to resolve this issue and
let me know if you have any concern regarding above version changes.
Hi Deep,
I'd suggest that we stabilize build first, do this change, and do a
complete build to ensure nothing breaks, and then commit, lest this would
potentially introduce more instability. There was an offline discussion
with Azeez et al on the same $subject.
Thanks,
Senaka.
On Mon, Mar 5,
On Mon, Mar 5, 2012 at 11:41 AM, Rajika Kumarasiri raj...@wso2.com wrote:
There is a dependency mismatch when I try to start Cassandra in Carbon
core with libthrift 0.8.0 ( carbon trunk libthrift version) but it works
fine with libthrift 0.6.1. Please advice me how to resolve this issue and
It seems the Cassandra version that you are using tightly couple into the
an older version of the thrift. In that case we will have to maintain both.
Rajika
On Mon, Mar 5, 2012 at 11:52 AM, Deependra Ariyadewa d...@wso2.com wrote:
On Mon, Mar 5, 2012 at 11:41 AM, Rajika Kumarasiri
On Mon, Mar 5, 2012 at 12:33 PM, Rajika Kumarasiri raj...@wso2.com wrote:
It seems the Cassandra version that you are using tightly couple into the
an older version of the thrift. In that case we will have to maintain both.
I checked Cassandra next version 1.1.x series and it depends on
11 matches
Mail list logo
