Thanks for your replies!
It is really a shame that is the way I would have to go. I am a contributor
for the Apache Gora[1] project and we were trying to support different
clients within our project but with those news, things really get
complicated :-/ maybe we will go with Intravert or DataStax
This is true for different open source projects with different objectives.
But IMHO Cassandra clients aim to solve one main problem which is to
provide access to Cassandra, and as they all have the same goal, shouldn't
they be aligned for the Cassandra community? I mean if we want to change
from
Hi Renato,
Are you sure that you don't have two copies of guava in your classpath? I
don't have this problem (I was using both Hector and Astyanax for a while
- now transitioned completely to Astyanax).
Probably the most problematic part of using the datastax or astyanax
clients is that they
This is a big Java problem with Guava and logging libraries that get
included with everything. If you bundle together enough projects you are
bound to have an satisfiable breaking mismatch. The hip trend is just use
the latest from mavenso hipsters have a canned reply, OMG!!! YOUR
VERSIONS IS SOO
I'll second that.
the maven boondoggle is a huge anti-practice for the java world.
On Sat, May 25, 2013 at 12:10 PM, Edward Capriolo edlinuxg...@gmail.comwrote:
This is a big Java problem with Guava and logging libraries that get
included with everything. If you bundle together enough
Hi all,
I am using Astyanax and Hector client within an application but right now I
am hitting a dependency issue [1] related to Guava version being used by
Hector and Astyanax which makes Maven headache. I have taken it out as
exclusions within my poms but I still get the dependency issue.
Do
