>
> every second minor release was fixing maven artifacts OR every second
> release was broken due the maven artifacts
Well, it's also possible just one release had 116 build artefact problems?
Obviously that's the absurd extreme end, but the reason I was asking if you
had any idea, since you'd d
Hey Benedict,
My replies in line
>> According to some recordings from DataStax there is a plan to support in
>> Cassandra multiple kinds of store - document, graph so it won’t get easier
>> with the time but rather harder - ask yourself do you really want to mess
>> all these things together?
> W
>
> According to some recordings from DataStax there is a plan to support in
> Cassandra multiple kinds of store - document, graph so it won’t get easier
> with the time but rather harder - ask yourself do you really want to mess
> all these things together?
Well, these certainly won't live in th
Sorry for not coming back to topic for long time.
You are right that what Cassandra project have currently - does work and
keeping package scoping discipline in such big development community as
Cassandra is clearly impossible without tool support (if you insist to keep ant
please try to separa
TL;DR - Benedict is right.
IMO Maven is a nice, straight-forward tool if you know what you’re doing and
start on a _new_ project.
But Maven easily becomes a pita if you want to do something that’s not
supported out-of-the-box.
I bet that Maven would just not work for C* source tree with all the
There are three distinct problems you raise: code structure, documentation,
and build system.
The build system, as far as I can tell, is a matter of personal preference.
I personally dislike the few interactions I've had with maven, but
gratefully my interactions with build system innards have bee
Hi all,
Not a cassandra contributor here, but I'm working on the cassandra sources
too.
This big cassandra source root caused me trouble too, firstly it was not
easy to import in an IDE, try to import cassandra sources in netbeans, it's
a headcache.
It would be great if we had more small modules
I think the problem is everyone currently contributing is comfortable with
ant, and as much as it is imperfect, it isn't clear maven is going to be
better. Having the requisite maven functionality linked under the hood
doesn't seem particularly preferable to the inverse. The status quo has the
bonu
Hey Tyler,
Thank you very much for coming back. I already lost faith that I will get
reply. :-) I am fine with code relocations. Moving constants into one place
where they cause no circular dependencies is cool, I’m all for doing such thing.
Currently Cassandra uses ant for doing some of maven f
Hi Łukasz,
I'm not very familiar with the build system, but I'll try to respond.
The Serializer dependencies on org.apache.cassandra.transport are almost
certainly uses of Server.CURRENT_VERSION and Server.VERSION_3. These are
constants that represent the native protocol version in use, which af
10 matches
Mail list logo
