On eaio.uuid version 3.4
TL;DR with the 3.4 release Johann has added a dependency to his library (to essentially use his own version of commons-io's IOUtils.closeQuietly) This brings a choice... Do I a) switch to a complete fork, change the package name, accept some other pull requests and try and build a community around the new one or b) create a rebuild of his grabbag project that gets pushed to Maven Central so I can pick up his changes and release 3.4.0 to match his 3.4 release See https://github.com/stephenc/eaio-uuid/pull/2 Comments on the pull request or here are appreciated. -Stephen
[RESULT] [VOTE] Release Mojo's Cassandra Maven Plugin 1.2.1-1
Result +1: Stephen Connolly, Mikhail Mazursky 0: Fred Cooke -1: -Stephen On 14 February 2013 09:28, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, I'd like to release version 1.2.1-1 of Mojo's Cassandra Maven Plugin to sync up with the 1.2.1 release of Apache Cassandra. We solved 1 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12121version=19089 Staging Repository: https://nexus.codehaus.org/content/repositories/orgcodehausmojo-015/ Site: http://mojo.codehaus.org/cassandra-maven-plugin/index.html SCM Tag: https://svn.codehaus.org/mojo/tags/cassandra-maven-plugin-1.2.1-1@17931 [ ] +1 Yeah! fire ahead oh and the blind man on the galloping horse says it looks fine too. [ ] 0 Mehhh! like I care, I don't have any opinions either, I'd follow somebody else if only I could decide who [ ] -1 No! wait up there I have issues (in general like, ya know, and being a trouble-maker is only one of them) The vote is open for 72h and will succeed by lazy consensus. Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Cheers -Stephen P.S. In the interest of ensuring (more is) better testing, and as is now tradition for Mojo's Cassandra Maven Plugin, this vote is also open to any subscribers of the dev and u...@cassandra.apache.org mailing lists that want to test or use this plugin.
[RESULT] [VOTE] Release Mojo's Cassandra Maven Plugin 1.2.0-1
This vote has passed:
+1: Stephen, Michael, Mikhail
0:
-1:
I will proceed with the promotion of artifacts to central
-Stephen
On 14 February 2013 06:26, Mikhail Mazursky ash...@gmail.com wrote:
+1. Please, release it.
2013/2/14 Stephen Connolly stephen.alan.conno...@gmail.com
More I'm looking for somebody who is actively sing C* to test it (there
are a couple of users... The lot f you who asked me to roll another
release). I will roll a 1.2.1 once I close this vote... I could close with
lazy consensus, but feel more comfortable if it has ad some testing ;-)
On Wednesday, 13 February 2013, Michael Kjellman wrote:
Considering that 1.2.1 is out, and looking at your project very quickly
(looks interesting)/overlaps a bit with CCMBridge no?/ I'd def say +1 :)
From: Stephen Connolly stephen.alan.conno...@gmail.commailto:
stephen.alan.conno...@gmail.com
Reply-To: u...@cassandra.apache.orgmailto:u...@cassandra.apache.org
u...@cassandra.apache.orgmailto:u...@cassandra.apache.org
Date: Wednesday, February 13, 2013 1:27 PM
To: d...@mojo.codehaus.orgmailto:d...@mojo.codehaus.org
d...@mojo.codehaus.orgmailto:d...@mojo.codehaus.org, dev
dev@cassandra.apache.orgmailto:dev@cassandra.apache.org,
u...@cassandra.apache.orgmailto:u...@cassandra.apache.org
u...@cassandra.apache.orgmailto:u...@cassandra.apache.org
Subject: Re: [VOTE] Release Mojo's Cassandra Maven Plugin 1.2.0-1
Ping
On Monday, 4 February 2013, Stephen Connolly wrote:
Hi,
I'd like to release version 1.2.0-1 of Mojo's Cassandra Maven Plugin
to sync up with the 1.2.0 release of Apache Cassandra. (a 1.2.1-1 will
follow shortly after this release, but it should be possible to use the
xpath://project/build/plugins/plugin/dependencies/dependency override of
cassandra-server to use C* releases from the 1.2.x stream now that the link
errors have been resolved, so that is less urgent)
We solved 1 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12121version=18467
Staging Repository:
https://nexus.codehaus.org/content/repositories/orgcodehausmojo-013/
Site:
http://mojo.codehaus.org/cassandra-maven-plugin/index.html
SCM Tag:
https://svn.codehaus.org/mojo/tags/cassandra-maven-plugin-1.2.0-1@17921
[ ] +1 Yeah! fire ahead oh and the blind man on the galloping horse
says it looks fine too.
[ ] 0 Mehhh! like I care, I don't have any opinions either, I'd
follow somebody else if only I could decide who
[ ] -1 No! wait up there I have issues (in general like, ya know,
and being a trouble-maker is only one of them)
The vote is open for 72h and will succeed by lazy consensus.
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Cheers
-Stephen
P.S.
In the interest of ensuring (more is) better testing, and as is now
tradition for Mojo's Cassandra Maven Plugin, this vote is
also open to any subscribers of the dev and u...@cassandra.apache.org
javascript:_e({},%20'cvml',%20'u...@cassandra.apache.org');
mailing lists that want to test or use this plugin.
[VOTE] Release Mojo's Cassandra Maven Plugin 1.2.1-1
Hi, I'd like to release version 1.2.1-1 of Mojo's Cassandra Maven Plugin to sync up with the 1.2.1 release of Apache Cassandra. We solved 1 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12121version=19089 Staging Repository: https://nexus.codehaus.org/content/repositories/orgcodehausmojo-015/ Site: http://mojo.codehaus.org/cassandra-maven-plugin/index.html SCM Tag: https://svn.codehaus.org/mojo/tags/cassandra-maven-plugin-1.2.1-1@17931 [ ] +1 Yeah! fire ahead oh and the blind man on the galloping horse says it looks fine too. [ ] 0 Mehhh! like I care, I don't have any opinions either, I'd follow somebody else if only I could decide who [ ] -1 No! wait up there I have issues (in general like, ya know, and being a trouble-maker is only one of them) The vote is open for 72h and will succeed by lazy consensus. Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Cheers -Stephen P.S. In the interest of ensuring (more is) better testing, and as is now tradition for Mojo's Cassandra Maven Plugin, this vote is also open to any subscribers of the dev and u...@cassandra.apache.org mailing lists that want to test or use this plugin.
Re: [VOTE] Release Mojo's Cassandra Maven Plugin 1.2.0-1
Ping
On Monday, 4 February 2013, Stephen Connolly wrote:
Hi,
I'd like to release version 1.2.0-1 of Mojo's Cassandra Maven Plugin
to sync up with the 1.2.0 release of Apache Cassandra. (a 1.2.1-1 will
follow shortly after this release, but it should be possible to use the
xpath://project/build/plugins/plugin/dependencies/dependency override of
cassandra-server to use C* releases from the 1.2.x stream now that the link
errors have been resolved, so that is less urgent)
We solved 1 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12121version=18467
Staging Repository:
https://nexus.codehaus.org/content/repositories/orgcodehausmojo-013/
Site:
http://mojo.codehaus.org/cassandra-maven-plugin/index.html
SCM Tag:
https://svn.codehaus.org/mojo/tags/cassandra-maven-plugin-1.2.0-1@17921
[ ] +1 Yeah! fire ahead oh and the blind man on the galloping horse
says it looks fine too.
[ ] 0 Mehhh! like I care, I don't have any opinions either, I'd
follow somebody else if only I could decide who
[ ] -1 No! wait up there I have issues (in general like, ya know,
and being a trouble-maker is only one of them)
The vote is open for 72h and will succeed by lazy consensus.
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Cheers
-Stephen
P.S.
In the interest of ensuring (more is) better testing, and as is now
tradition for Mojo's Cassandra Maven Plugin, this vote is
also open to any subscribers of the dev and
u...@cassandra.apache.orgjavascript:_e({}, 'cvml',
'u...@cassandra.apache.org');
mailing lists that want to test or use this plugin.
Re: [VOTE] Release Mojo's Cassandra Maven Plugin 1.2.0-1
More I'm looking for somebody who is actively sing C* to test it (there are
a couple of users... The lot f you who asked me to roll another release). I
will roll a 1.2.1 once I close this vote... I could close with lazy
consensus, but feel more comfortable if it has ad some testing ;-)
On Wednesday, 13 February 2013, Michael Kjellman wrote:
Considering that 1.2.1 is out, and looking at your project very quickly
(looks interesting)/overlaps a bit with CCMBridge no?/ I'd def say +1 :)
From: Stephen Connolly stephen.alan.conno...@gmail.com javascript:;
mailto:stephen.alan.conno...@gmail.com javascript:;
Reply-To: u...@cassandra.apache.org javascript:;mailto:
u...@cassandra.apache.org javascript:;
u...@cassandra.apache.orgjavascript:;
mailto:u...@cassandra.apache.org javascript:;
Date: Wednesday, February 13, 2013 1:27 PM
To: d...@mojo.codehaus.org
javascript:;mailto:d...@mojo.codehaus.orgjavascript:;
d...@mojo.codehaus.org
javascript:;mailto:d...@mojo.codehaus.orgjavascript:;,
dev dev@cassandra.apache.org javascript:;mailto:
dev@cassandra.apache.org javascript:;,
u...@cassandra.apache.orgjavascript:;
mailto:u...@cassandra.apache.org javascript:;
u...@cassandra.apache.org
javascript:;mailto:u...@cassandra.apache.orgjavascript:;
Subject: Re: [VOTE] Release Mojo's Cassandra Maven Plugin 1.2.0-1
Ping
On Monday, 4 February 2013, Stephen Connolly wrote:
Hi,
I'd like to release version 1.2.0-1 of Mojo's Cassandra Maven Plugin
to sync up with the 1.2.0 release of Apache Cassandra. (a 1.2.1-1 will
follow shortly after this release, but it should be possible to use the
xpath://project/build/plugins/plugin/dependencies/dependency override of
cassandra-server to use C* releases from the 1.2.x stream now that the link
errors have been resolved, so that is less urgent)
We solved 1 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12121version=18467
Staging Repository:
https://nexus.codehaus.org/content/repositories/orgcodehausmojo-013/
Site:
http://mojo.codehaus.org/cassandra-maven-plugin/index.html
SCM Tag:
https://svn.codehaus.org/mojo/tags/cassandra-maven-plugin-1.2.0-1@17921
[ ] +1 Yeah! fire ahead oh and the blind man on the galloping horse
says it looks fine too.
[ ] 0 Mehhh! like I care, I don't have any opinions either, I'd
follow somebody else if only I could decide who
[ ] -1 No! wait up there I have issues (in general like, ya know,
and being a trouble-maker is only one of them)
The vote is open for 72h and will succeed by lazy consensus.
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Cheers
-Stephen
P.S.
In the interest of ensuring (more is) better testing, and as is now
tradition for Mojo's Cassandra Maven Plugin, this vote is
also open to any subscribers of the dev and
u...@cassandra.apache.orgjavascript:;
javascript:_e({},%20'cvml',%20'u...@cassandra.apache.org javascript:;
');
mailing lists that want to test or use this plugin.
Re: [VOTE] Release Mojo's Cassandra Maven Plugin 1.0.0-1
On 3 May 2012 10:04, Radim Kolar h...@filez.com wrote: I'd like to release version 1.1.0-1 of Mojo's Cassandra Maven Plugin What is this plugin supposed to do? Mojo's Cassandra Plugin is used when you want to control a test instance of Apache Cassandra from within your Apache Maven build. Useful for integration testing / webapp development as the developer gets their own test instance and doesn't have to have installed anything on their machine to get it. Have a look at the plugin's website, specifically: http://mojo.codehaus.org/cassandra-maven-plugin/examples/developing-webapp.html and http://mojo.codehaus.org/cassandra-maven-plugin/examples/integration-tests.html For a lot of testing strategies, people may fire up cassandra instances directly from the JUnit test case so that tests can be run via the IDE, but for more complex testing where you need more infra set-up this plugin starts to really shine... oh and live webapp development like mvn cassandra:run jetty:run where you don't have a unit test in scope to start up cassandra HTH
[VOTE] Release Mojo's Cassandra Maven Plugin 1.0.0-1
Hi, I'd like to release version 1.1.0-1 of Mojo's Cassandra Maven Plugin to sync up with the 1.1.0 release of Apache Cassandra. We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12121version=17926 Staging Repository: https://nexus.codehaus.org/content/repositories/orgcodehausmojo-068/ Site: http://mojo.codehaus.org/cassandra-maven-plugin/index.html SCM Tag: https://svn.codehaus.org/mojo/tags/cassandra-maven-plugin-1.1.0-1@16519 [ ] +1 Yeah! fire ahead oh and the blind man on the galloping horse says it looks fine too. [ ] 0 Mehhh! like I care, I don't have any opinions either, I'd follow somebody else if only I could decide who [ ] -1 No! wait up there I have issues (in general like, ya know, and being a trouble-maker is only one of them) The vote is open for 72h and will succeed by lazy consensus. Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Cheers -Stephen P.S. In the interest of ensuring (more is) better testing, this vote is also open to subscribers of the dev and u...@cassandra.apache.org mailing lists.
Re: Inconsistent dependencies
On 25 April 2012 09:00, Stephen Connolly stephen.alan.conno...@gmail.comwrote: On 25 April 2012 08:39, Matthias Pfau p...@l3s.de wrote: Hi there, yesterday, we noticed that cassandra is currently published with inconsistent dependencies. The inconsistencies exist between the published pom and the published distribution (tar.gz). This is a serious issue for us as we are using pom dependencies for development/testing and a tarball distribution for production. I have read https://issues.apache.org/**jira/browse/CASSANDRA-850https://issues.apache.org/jira/browse/CASSANDRA-850and understood that you version all runtime dependencies in lib/ because you have to update license files manually and therefore see no benefit in using ivy. Not using ivy any more, switched to Maven ANT tasks but same difference. However, I would like to make the following proposals for solving the described issue: a.) don't put everything from lib/ on the compile classpath but rather each library individually. Extract the versions into constants that are used to put the jars from lib/ onto the classpath and to generate a consistent pom. Makes some occasionally invalid assumptions about lib folder versioning and maven repo versioning. b.) go a step back and don't version any jars in lib/ but automate the retrieval of license files (would do this for you, if needed) I'd be interested in seeing what reaction you get to this... I suggested it a while back, but got nowhere c.) create a fat-jar of all dependencies or relabel all dependencies and publish them to the maven repo, too God no. not c) What do you think? I am also interested in knowing what you do to workaround this problem! And if it is not a problem for you, please tell me why... Every so often, I get some cycles free and I check the pom for being valid and push patches to the C* devs. I haven't had many cycles in the 1.0.x suite of releases. the 0.8.x set should be fairly close, I think only 1 or 2 releases escaped with different dependencies. Also, for 1 or 2 dependencies, they are exactly the same but the checksums differ due to timestamp changes, a deep diff of the bytecode reveals that the dependencies are effectively the same. Due to having bigger fish to fry, for those deps I have not bothered fighting to get the lib version changed. In general, maintaining the pom is something that can fall off the C* devs radar... in part because some of the devs are not interested in generating poms (I suspect as a result of being burned by some of the woefully bad maven builds I have seen some people force on people [virtually looks at co-worker and shakes head]) and in part because most of the devs are not Maven people and so do not fully grok the pom itself. I will take a quick look and see if I can push a patch, sylvain or jonathan are usually happy to apply them for me. https://issues.apache.org/jira/browse/CASSANDRA-4183 created. Note that those two dependencies look to be the only critical diffs. The other diffs are just purely cosmetic by my analysis. Kind regards Matthias
Re: What's the point of the deviation of java code style in Cassandra?
http://programmers.stackexchange.com/questions/2715/should-curly-braces-appear-on-their-own-line
On 27 January 2012 11:36, bxqdev bxq...@themailbay.com wrote:
Hello, Cassandra Developers!
What's the point of the deviation (important exception) from the Sun's
Java coding convention in Cassandra's java code Style:
{ and } are always placed on a new line
Why is that??
thanks.
Re: What's the point of the deviation of java code style in Cassandra?
You perhaps are not a veteran of the braces wars of 1973-2011...
Please don't try to start them up again!
Every project has its own style. Stick to that style.
There is no standard style, Sun's convention is just the style they tried
to enforce on their own codebase... I should point out that they didn't
enforce it there either.
Many a developer was left wounded on the battlefield in those braces
wars... let's hope more do not have to follow
On 27 January 2012 11:57, bxqdev bxq...@themailbay.com wrote:
i guess you mean it's not a constructive question.
it would be, it there wasn't a standard: Sun's Java coding convention,
which already says how to place curly braces correctly.
why deviate from the de facto standard for no reason?
thanks.
On 1/27/2012 3:48 PM, Stephen Connolly wrote:
http://programmers.**stackexchange.com/questions/**
2715/should-curly-braces-**appear-on-their-own-linehttp://programmers.stackexchange.com/questions/2715/should-curly-braces-appear-on-their-own-line
On 27 January 2012 11:36, bxqdevbxq...@themailbay.com wrote:
Hello, Cassandra Developers!
What's the point of the deviation (important exception) from the Sun's
Java coding convention in Cassandra's java code Style:
{ and } are always placed on a new line
Why is that??
thanks.
Re: Cassandra has moved to Git
just the question, where do us contributors who are not committers but have cla's on file (ie already asf committers) push our changes? hoping this change will make contributing easier. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 28 Dec 2011 19:56, Eric Evans eev...@acunu.com wrote: While this is something we had talked about for ages, the actual switch-over happened rather abruptly, and Cassandra's canonical repository is now hosted in Git. For instructions on getting started, see https://git-wip-us.apache.org. We've also started putting random administrivia in the wiki at http://wiki.apache.org/cassandra/GitTransition. The Github mirror (http://github.com/apache/cassandra) hasn't been seeing updates since the move, but that will be fixed at some point. The important thing is that they share identical histories, so new (or existing forks) are forward-compatible. There are a few outstanding items being worked on (CI systems for example), but if you notice something that's been missed don't hesitate to speak up. The website will be updated as soon as SVN is unlocked. There are also some matters of work-flow or process that we need to hashed out. For example, how do we handle reviews now? Do we continue to mandate/recommend/allow rebasing? Thoughts? -- Eric Evans Acunu | http://www.acunu.com | @acunu
Re: [VOTE] Release Mojo's Cassandra Maven Plugin 1.0.0-1
Nobody objects, so I will publish the artifacts as Cassandra 1.0.0 is being released On 12 October 2011 23:44, Stephen Connolly stephen.alan.conno...@gmail.comwrote: Hi, I'd like to release version 1.0.0-1 of Mojo's Cassandra Maven Plugin to sync up with the pending 1.0.0 release of Apache Cassandra. This version needs to be tested in conjunction with the current staging repo for Cassandra 1.0.0 We solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12121version=17828 Staging Repository: https://nexus.codehaus.org/content/repositories/orgcodehausmojo-010/ Site: http://mojo.codehaus.org/cassandra-maven-plugin/index.html SCM Tag: https://svn.codehaus.org/mojo/tags/cassandra-maven-plugin-1.0.0-1@14818 [ ] +1 Yeah! fire ahead oh and the blind man on the galloping horse says it looks fine too. [ ] 0 Mehhh! like I care, I don't have any opinions either, I'd follow somebody else if only I could decide who [ ] -1 No! wait up there I have issues (in general like, ya know, and being a trouble-maker is only one of them) The vote is open for until Cassandra 1.0.0 is released and will succeed by lazy consensus. Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Cheers -Stephen P.S. In the interest of ensuring (more is) better testing, this vote is also open to subscribers of the dev and u...@cassandra.apache.org mailing lists
Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 3
+1 (non-binding) tested with cassandra-maven-plugin -Stephen On 11 October 2011 16:26, Sylvain Lebresne sylv...@datastax.com wrote: Let's hope third times will be the charm. With #3343, #3345 and #3346 in, I propose the following artifacts for release as 1.0.0. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0.0@r1181820 Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-055/org/apache/cassandra/apache-cassandra/1.0.0/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-055/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/tNca8 (CHANGES.txt) [2]: http://goo.gl/qVAIU (NEWS.txt)
[VOTE] Release Mojo's Cassandra Maven Plugin 1.0.0-1
Hi, I'd like to release version 1.0.0-1 of Mojo's Cassandra Maven Plugin to sync up with the pending 1.0.0 release of Apache Cassandra. This version needs to be tested in conjunction with the current staging repo for Cassandra 1.0.0 We solved 1 issue: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12121version=17828 Staging Repository: https://nexus.codehaus.org/content/repositories/orgcodehausmojo-010/ Site: http://mojo.codehaus.org/cassandra-maven-plugin/index.html SCM Tag: https://svn.codehaus.org/mojo/tags/cassandra-maven-plugin-1.0.0-1@14818 [ ] +1 Yeah! fire ahead oh and the blind man on the galloping horse says it looks fine too. [ ] 0 Mehhh! like I care, I don't have any opinions either, I'd follow somebody else if only I could decide who [ ] -1 No! wait up there I have issues (in general like, ya know, and being a trouble-maker is only one of them) The vote is open for until Cassandra 1.0.0 is released and will succeed by lazy consensus. Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Cheers -Stephen P.S. In the interest of ensuring (more is) better testing, this vote is also open to subscribers of the dev and u...@cassandra.apache.org mailing lists
Re: svn commit: r1180970 - in /cassandra/branches/cassandra-1.0.0: ./ src/java/org/apache/cassandra/db/ src/java/org/apache/cassandra/db/compaction/ src/java/org/apache/cassandra/io/sstable/ src/java/
Yeah it was my bad... the patch for the build versions included an extra .3...
when reviewing the pom for the 1.0.0 vote I caught the mis-match...
pinged Sylvain on IRC...
should probably have raised a JIRA...
but the issue could at best affect only windows users running
cassandra embedded in their build via maven...
not even sure it would affect them given the changes between 1.0.3 and 1.0.3.3
but safer to use the _exact_ same version
-Stephen
On 10 October 2011 15:19, Norman Maurer norman.mau...@googlemail.com wrote:
No problem... It just catched my attention ;)
Keep on coding,
Norman
2011/10/10 Sylvain Lebresne sylv...@datastax.com:
On Mon, Oct 10, 2011 at 4:03 PM, Norman Maurer
norman.mau...@googlemail.com wrote:
Hi there,
did you alter the snappy-java version by mistake or was this part of
the commit ?
Sorry, that was intentional but I should probably not have been lazy
and made a separate commit.
I just updated the version referenced in the pom so that it matches
what we are using. i.e, I
haven't updated the lib, I've just made it so that user of maven
central will get the 'right' version.
--
Sylvain
Bye,
Norman
2011/10/10 slebre...@apache.org:
Author: slebresne
Date: Mon Oct 10 13:56:27 2011
New Revision: 1180970
URL: http://svn.apache.org/viewvc?rev=1180970view=rev
Log:
Fix places where uncompressed sstable size is used in place of the
compressed one.
patch by slebresne; reviewed by jbellis for CASSANDRA-3338
Modified:
cassandra/branches/cassandra-1.0.0/CHANGES.txt
cassandra/branches/cassandra-1.0.0/build.xml
cassandra/branches/cassandra-1.0.0/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
cassandra/branches/cassandra-1.0.0/src/java/org/apache/cassandra/db/compaction/CompactionManager.java
cassandra/branches/cassandra-1.0.0/src/java/org/apache/cassandra/db/compaction/SizeTieredCompactionStrategy.java
cassandra/branches/cassandra-1.0.0/src/java/org/apache/cassandra/io/sstable/SSTable.java
cassandra/branches/cassandra-1.0.0/src/java/org/apache/cassandra/io/sstable/SSTableReader.java
cassandra/branches/cassandra-1.0.0/src/java/org/apache/cassandra/io/util/CompressedSegmentedFile.java
cassandra/branches/cassandra-1.0.0/src/java/org/apache/cassandra/io/util/SegmentedFile.java
Modified: cassandra/branches/cassandra-1.0.0/CHANGES.txt
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-1.0.0/CHANGES.txt?rev=1180970r1=1180969r2=1180970view=diff
==
--- cassandra/branches/cassandra-1.0.0/CHANGES.txt (original)
+++ cassandra/branches/cassandra-1.0.0/CHANGES.txt Mon Oct 10 13:56:27 2011
@@ -12,6 +12,8 @@
* run compaction and hinted handoff threads at MIN_PRIORITY
(CASSANDRA-3308)
* default hsha thrift server to cpu core count in rpc pool
(CASSANDRA-3329)
* add bin\daemon to binary tarball for Windows service (CASSANDRA-3331)
+ * Fix places where uncompressed size of sstables was use in place of the
+ compressed one (CASSANDRA-3338)
Fixes merged from 0.8 below:
* Fix tool .bat files when CASSANDRA_HOME contains spaces (CASSANDRA-3258)
* Force flush of status table when removing/updating token
(CASSANDRA-3243)
Modified: cassandra/branches/cassandra-1.0.0/build.xml
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-1.0.0/build.xml?rev=1180970r1=1180969r2=1180970view=diff
==
--- cassandra/branches/cassandra-1.0.0/build.xml (original)
+++ cassandra/branches/cassandra-1.0.0/build.xml Mon Oct 10 13:56:27 2011
@@ -350,7 +350,7 @@ url=${svn.entry.url}?pathrev=${svn.entry
license name=The Apache Software License, Version 2.0
url=http://www.apache.org/licenses/LICENSE-2.0.txt/
scm connection=${scm.connection}
developerConnection=${scm.developerConnection} url=${scm.url}/
dependencyManagement
- dependency groupId=org.xerial.snappy
artifactId=snappy-java version=1.0.3.3/
+ dependency groupId=org.xerial.snappy
artifactId=snappy-java version=1.0.3/
dependency groupId=com.ning artifactId=compress-lzf
version=0.8.4/
dependency groupId=com.google.guava artifactId=guava
version=r08/
dependency groupId=commons-cli artifactId=commons-cli
version=1.1/
Modified:
cassandra/branches/cassandra-1.0.0/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
URL:
http://svn.apache.org/viewvc/cassandra/branches/cassandra-1.0.0/src/java/org/apache/cassandra/db/ColumnFamilyStore.java?rev=1180970r1=1180969r2=1180970view=diff
==
---
cassandra/branches/cassandra-1.0.0/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
(original)
+++
cassandra/branches/cassandra-1.0.0/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
Mon Oct 10
Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2
+1 (non-binding) -Stephen On 10 October 2011 17:24, Sylvain Lebresne sylv...@datastax.com wrote: As said while closing previous vote, CASSANDRA-3338 felt important enough to warrant a reroll. So here it is: I propose the following artifacts for release as 1.0.0 (those are the same as the previous + the patch for CASSANDRA-3338 and a one line fix to the build file so that it picks the right version of snappy-java from maven central). SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0.0@r1180970 Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-046/org/apache/cassandra/apache-cassandra/1.0.0/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-046/ The artifacts as well as the debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/JB2NL (CHANGES.txt) [2]: http://goo.gl/x6gTC (NEWS.txt)
Re: [VOTE] Release Apache Cassandra 1.0.0-rc1 (Release Candidate 1)
+1 on the POMs (non-Binding) -Stephen On 26 September 2011 13:37, Sylvain Lebresne sylv...@datastax.com wrote: The first beta played its role well: bugs, small and bigger, were fixed[1]. We have no ticket left open for 1.0.0 except for a few that are minor, aren't regressions and imho are no blocker as far as the release of 1.0.0 is concerned. So proceeding with our plan, I think the final release is around the corner and I thus propose the following artifacts for release as 1.0.0-rc1. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0.0@r1175771 Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-103/org/apache/cassandra/apache-cassandra/1.0.0-rc1/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-103/ The artifacts as well as a debian package are also available here: http://people.apache.org/~slebresne/ Since the beta 1 release has been overall rather calm, given this not a final release (yet) and in order to stick to the schedule as much as we can, I propose a short 24h vote (longer if needed). [1]: http://goo.gl/9z2yt (CHANGES.txt) [2]: http://goo.gl/UUYJY (NEWS.txt)
Re: [VOTE] Release Mojo's Cassandra Maven Plugin 0.8.6-1
This vote has passed: +1: Me, Colin Nate 0: -1: I will proceed with the release -Stephen On 20 September 2011 15:27, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, I'd like to release version 0.8.6-1 of Mojo's Cassandra Maven Plugin to sync up with the recent 0.8.6 release of Apache Cassandra. We solved 2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12121version=17425 Staging Repository: https://nexus.codehaus.org/content/repositories/orgcodehausmojo-010/ Site: http://mojo.codehaus.org/cassandra-maven-plugin/index.html SCM Tag: https://svn.codehaus.org/mojo/tags/cassandra-maven-plugin-0.8.6-1@14748 [ ] +1 Yeah! fire ahead oh and the blind man on the galloping horse says it looks fine too. [ ] 0 Mehhh! like I care, I don't have any opinions either, I'd follow somebody else if only I could decide who [ ] -1 No! wait up there I have issues (in general like, ya know, and being a trouble-maker is only one of them) The vote is open for 72 hours and will succeed by lazy consensus. Cheers -Stephen P.S. In the interest of ensuring (more is) better testing, this vote is also open to subscribers of the dev and u...@cassandra.apache.org mailing lists
Re: The Eclipse target doesn't seem to show up in 'ant -p'
do a realclean - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 7 Sep 2011 19:21, Jason Rutherglen jason.rutherg...@gmail.com wrote: Now something is broken, I stopped my laptop while Maven was downloading something! --- Buildfile: /home/j/src/CASSANDRA-3147/build.xml maven-ant-tasks-localrepo: maven-ant-tasks-download: maven-ant-tasks-init: Unable to obtain resource from /home/j/src/CASSANDRA-3147/build/maven-ant-tasks-2.1.3.jar: java.util.zip.ZipException: error in opening zip file [typedef] Unable to obtain resource from /home/j/src/CASSANDRA-3147/build/maven-ant-tasks-2.1.3.jar: [typedef] java.util.zip.ZipException: error in opening zip file [typedef] at java.util.zip.ZipFile.open(Native Method) [typedef] at java.util.zip.ZipFile.init(ZipFile.java:127) [typedef] at java.util.jar.JarFile.init(JarFile.java:135) [typedef] at java.util.jar.JarFile.init(JarFile.java:99) [typedef] at org.apache.tools.ant.AntClassLoader.getResourceURL(AntClassLoader.java:1002) [typedef] at org.apache.tools.ant.AntClassLoader$ResourceEnumeration.findNextResource(AntClassLoader.java:145) [typedef] at org.apache.tools.ant.AntClassLoader$ResourceEnumeration.init(AntClassLoader.java:109) [typedef] at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:949) [typedef] at org.apache.tools.ant.AntClassLoader.getNamedResources(AntClassLoader.java:918) [typedef] at org.apache.tools.ant.loader.AntClassLoader5.getResources(AntClassLoader5.java:54) [typedef] at org.apache.tools.ant.taskdefs.Definer.resourceToURLs(Definer.java:375) [typedef] at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:267) [typedef] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) [typedef] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) [typedef] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [typedef] at java.lang.reflect.Method.invoke(Method.java:597) [typedef] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) [typedef] at org.apache.tools.ant.Task.perform(Task.java:348) [typedef] at org.apache.tools.ant.Target.execute(Target.java:390) [typedef] at org.apache.tools.ant.Target.performTasks(Target.java:411) [typedef] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397) [typedef] at org.apache.tools.ant.Project.executeTarget(Project.java:1366) [typedef] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) [typedef] at org.apache.tools.ant.Project.executeTargets(Project.java:1249) [typedef] at org.apache.tools.ant.Main.runBuild(Main.java:801) [typedef] at org.apache.tools.ant.Main.startAnt(Main.java:218) [typedef] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) [typedef] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) [typedef] Could not load definitions from resource org/apache/maven/artifact/ant/antlib.xml. It could not be found. BUILD FAILED /home/j/src/CASSANDRA-3147/build.xml:290: Problem: failed to create task or type antlib:org.apache.maven.artifact.ant:remoteRepository Cause: The name is undefined. Action: Check the spelling. Action: Check that any custom tasks/types have been declared. Action: Check that any presetdef/macrodef declarations have taken place. No types or tasks have been defined in this namespace yet This appears to be an antlib declaration. Action: Check that the implementing library exists in one of: -/usr/share/ant/lib -/home/j/.ant/lib -a directory added on the command line with the -lib argument Total time: 1 second
Re: Proposal: Moving CQL drivers
On 7 September 2011 10:12, Eric Evans eev...@acunu.com wrote: On Wed, Sep 7, 2011 at 8:22 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 6 September 2011 18:34, Vivek Mishra vivek.mis...@yahoo.com wrote: Sounds good moving to github. 1 quick question, what about JIRAs already raised w.r.t drivers? Not sure but is it possible to integrate these new projects with current JIRA flow? Planning to make these new projects based on maven build process?(As that might be helpful in case of any quick release required for any sub module). Ha! I would be genuinely surprised if that were to happen. I think there is a greater chance of seeing C* itself being built with maven than the drivers... Really? I see the exact opposite, (and it's probably no secret how I feel about Maven). Hmmm, well here's my view, the only ones where Maven makes sense are the JVM based drivers. Most of the JVM based ones can be simplified down to the JDBC driver... and as Eric is the driver of the JDBC driver and Eric's opinions on Maven are well known... P.S. I will wait to be asked for my opinion on how this could be addresses using Maven as a build tool. Is that, Through the use of copious amounts of XML markup, storage, and network bandwidth?. :) Meh, the XML would be an order of magnitude less than the current ANT build script. Storage... well it depends which storage you are talking about, it would be a choice of storage in .svn or storage in ~/.m2 Network bandwidth... only if people follow poor -SNAPSHOT strategies and are constantly deploying -SNAPSHOTs to the remote repo Sorry, I couldn't resist. Neither could I ;-) The stated preference of the C* developers is to use ANT. I am happy that Maven ANT Tasks is being used over IVY, and happy that the artifacts are being pushed to central, after that it doesn't matter what the build tool used is, as long as the published poms are good (and last time I fine tuned them they were) and as long as stuff gets into central, I am fine. -- Eric Evans Acunu | http://www.acunu.com | @acunu
Re: Reoganizing drivers
On 13 July 2011 00:47, Jonathan Ellis jbel...@gmail.com wrote:
On Sat, Jul 9, 2011 at 8:29 PM, Rick Shaw wfs...@gmail.com wrote:
On Jul 7, 2011, at 10:53 AM, Eric Evans wrote:
On Wed, 2011-07-06 at 13:33 -0500, Jonathan Ellis wrote:
- the git mirror won't pick up anything under drivers/
Has there been any effort made to have INFRA add it?
Aaron asked, they said they only do standard svn trunk + branches + tags.
But I think what they mean is that you'd need to tweak things a little, e.g.
svn mkdir http://svn.apache.org/repos/asf/cassandra/server
svn mv http://svn.apache.org/repos/asf/cassandra/trunk
http://svn.apache.org/repos/asf/cassandra/tags
http://svn.apache.org/repos/asf/cassandra/branches
http://svn.apache.org/repos/asf/cassandra/server/
svn mkdir http://svn.apache.org/repos/asf/cassandra/drivers/trunk
svn mv http://svn.apache.org/repos/asf/cassandra/drivers/java
http://svn.apache.org/repos/asf/cassandra/drivers/py
http://svn.apache.org/repos/asf/cassandra/drivers/trunk/
and basically end up with at the
http://svn.apache.org/repos/asf/cassandra/ a set of directories with
trunk/tags/branches underneath.
In fact I suspect you would not even have to move the main branches
(which would be better for svn mergeinfo) as they should be able to
retain the git repo for that as is and just by structuring the drivers
directory with a trunk/tags/branches (and sure keep branches empty if
you want) they could give you
git://git.apache.org/cassandra-drivers.git for the drivers and
git://git.apache.org/cassandra.git remains in place and as is for the
core/server
if they give you any hassle just point out that they do this already
for mina, myfaces, maven, etc... and if it is a big issue you can
always rename cassandra to massandra as they seem to do it for any
project beinging with m ;-)
What do you mean by but not have multiple versions for 0.8 branch?
I mean it would live in trunk but only in trunk -- there would be no
branches/0.8/drivers or branches/1.0/drivers.
Can't we keep the /drivers code in the trunk and just have separate Ant
tasks for building the driver parts independent of the tasks for for the
server?
Right, this feels ideal to me. Otherwise the right way to handle it
is to download a Cassandra stuff-the-driver-needs jar from the maven
repo.
I will be providing a patch that will allow deploying -SNAPSHOTs to
the apache snapshot repository once I get some releases off the decks
at Maven, that will make life easier for the Hector guys etc (as they
can follow trunk more easily, and push -SNAPSHOTs themselves to allow
for easier user testing) but a side-effect is that it would make life
easier if you went with this approach... and remember that the maven
repo in this case does not even need to go off your machine as you can
just install the core deps in your local repo by doing a build of core
locally.
I'd rather just have {cassandra} and {driver} build targets
personally, from the same tree, rather than introducing this
intermediate dependency.
It does bring up versioning... the tag for drivers releases will
include cassandra stuff too... I have the feeling that you cannot have
your cake and eat it too
Another thought would be to keep it in the separate tree as it is now, and
dumb down the driver build to just build the JAR artifacts (binary, source,
and javadoc). and do all testing and integration work in the server-side
trunk by using just the Driver jar as a dependency for the tests in the
server tree?
Then you have the reverse problem, that running the test suite
requires this other checkout to be around somewhere.
But the driver jar is supposed to be more stable, and have a much
slower release cadence. I see much less of an issue pulling the driver
jar from the (local/remote) maven repo than pulling the core stuff.
I would see this option as being closer to the way you guys seem to
want to work...
But I will raise this one question
The tension seems to be between whether to re-release a drivers jar
with every core release, or have it with its own release cadence. To
my mind, from the Maven Pom point-of-view as long as the drivers
depend on core classes (and that includes thrift) it needs to at least
match the release cadence of core releases (i.e. you would need one
release for each release of core, and if it needs its own bug-fixes
they would be extra releases)
The major pain for releasing the drivers jar is that you have to test
it... building it is no big shakes but testing is where the effort
lies. Now the testing effort has to happen anyway at the main core
release cadence, because even if you think you don't need to rebuild
drivers for the core 0.8.2 release, you do need to test that the
drivers jar you tested against 0.8.1 still works [or at least do some
investigation to say that the changes cannot affect it working...
chaos butterflies will still want testing though*] and that is
ignoring the Maven Pom issue§
So here is the
Re: Reoganizing drivers
munch munch munch... this popcorn is nice... having a hard time keeping stum... :-) - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 10 Jul 2011 04:30, Rick Shaw wfs...@gmail.com wrote: On Jul 7, 2011, at 10:53 AM, Eric Evans wrote: On Wed, 2011-07-06 at 13:33 -0500, Jonathan Ellis wrote: - the git mirror won't pick up anything under drivers/ Has there been any effort made to have INFRA add it? It was separated out to make it look/act like an independent project. Cant we get an additional GIT project for drivers? - building the Java drivers is fragile and complicated, and there's a lot of duplication with the main ant build Fragile how so? Because of the build-dependency on Cassandra (and/or how it is satisfied)? Yes. What duplication are you referring to? I don't see much beyond all of the boilerplate you'd see between any two ant projects. Wow I would hardly call the current build for C* boilerplate. It is quite comprehensive but very elaborate and complicate. A lot of clever expertise has been applied. Duplicating the necessary functionality and reaching into another existing source tree is just complicated and error prone. Not impossible, but fragile seems a good description. - patches that affect both Cassandra and JDBC are cumbersome since they have to be committed separately (e.g. https://issues.apache.org/jira/browse/CASSANDRA-2857) Well, the idea of moving it was to be able to treat it as a separate project (more or less), so it follows that you'd have to independently patch anything using AbstractCassandraDaemon. This is a problem that cant be helped if they are separate projects. RIght? Well, it follows that if we change an API that any project using it will need to be updated as well. Since the idea behind moving the drivers was to be able to treat them as separate projects, it follows that we'd have to do it here as well. I'm inclined to think we should move it back to trunk (but not have multiple versions for 0.8 branch). We can still tag/branch separately from there. What do you mean by but not have multiple versions for 0.8 branch? I like the idea of it being being built as a separate project. But I also like it being in the main trunk. Is it possible to have both? Can't we keep the /drivers code in the trunk and just have separate Ant tasks for building the driver parts independent of the tasks for for the server? Another thought would be to keep it in the separate tree as it is now, and dumb down the driver build to just build the JAR artifacts (binary, source, and javadoc). and do all testing and integration work in the server-side trunk by using just the Driver jar as a dependency for the tests in the server tree? -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release Apache Cassandra 0.7.6
You appear to be missing the -bin artifacts from the staging repository. On 13 May 2011 10:39, Sylvain Lebresne sylv...@datastax.com wrote: It's been only a little more than 2 weeks since the release of 0.7.5, but since then we have corrected a handfull of fairly important bugs, incuding: https://issues.apache.org/jira/browse/CASSANDRA-2554 https://issues.apache.org/jira/browse/CASSANDRA-2633 https://issues.apache.org/jira/browse/CASSANDRA-2552 I thus propose the following artifacts for release as 0.7.6. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1102594 Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-010/org/apache/cassandra/apache-cassandra/0.7.6/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-010 The artifacts as well as a debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours (longer if needed). [1]: http://goo.gl/VYZ2e (CHANGES.txt) [2]: http://goo.gl/jMRDE (NEWS.txt) -- Sylvain
Re: [VOTE] Release Apache Cassandra 0.8.0 rc1
The stage artifacts look good from a Maven PoV. I'll be testing them later. Hopefully this time you'll not forget to release the staging repo ;-) [aside] When can we expect to see release votes for CQL (and if you need me to help with getting that into Maven central, just shout) -Stephen On 11 May 2011 01:46, Eric Evans eev...@rackspace.com wrote: I propose the following artifacts for release as 0.8.0 RC1. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1101689 Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-004/ Driver Artifacts and Debian Package: http://people.apache.org/~eevans The will remain open for 72 hours, (longer if need be). [1]: http://goo.gl/fsaH8 (CHANGES.txt) [2]: http://goo.gl/IWE0T (NEWS.txt) -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release Apache Cassandra 0.8.0 rc1
On 11 May 2011 15:16, Eric Evans eev...@rackspace.com wrote: On Wed, 2011-05-11 at 11:53 +0100, Stephen Connolly wrote: When can we expect to see release votes for CQL (and if you need me to help with getting that into Maven central, just shout) Not sure what you mean. The driver is part of this vote, it's in my home directory on people.a.o. https://repository.apache.org/content/repositories/orgapachecassandra-004/org/apache/cassandra/ I see no cassandra-cql (Because we took it out of the publish to central over a disagreement on version numbering and release scheduling) On 11 May 2011 01:46, Eric Evans eev...@rackspace.com wrote: Driver Artifacts and Debian Package: http://people.apache.org/~eevans -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release Apache Cassandra 0.8.0-beta1 artifacts in Maven Central
ping. still waiting for two more +1's from cassandra committers - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 29 Apr 2011 14:02, Stephen Connolly stephen.alan.conno...@gmail.com wrote: OK CQL has been dropped from this release, I need two more binding +1's to release what remains (all thrift) On 28 April 2011 20:42, Stephen Connolly stephen.alan.conno...@gmail.com wrote: ok well I will see about deleting it from the staging repo, can I get a conditional + 1 on that basis? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 28 Apr 2011 20:31, Eric Evans eev...@rackspace.com wrote: On Thu, 2011-04-28 at 16:44 +0100, Stephen Connolly wrote: Unlike the RPC, CQL is meant to be stable. It is a significant feature that you should be able to use the same version of a driver across many versions of Cassandra. This is why the versions must be different, so that you can evaluate each new driver version in the context of how it changed, not (necessarily )how Cassandra changed during some arbitrary release. This version number is all about versioning the information in the __pom__. The pom defines transitive dependencies. You might not rebuild the cql jar at all, but keep redeploying with different poms (each getting their own version number... because we can only use a version number once)... yes that is somewhat wasteful of space on the central repository, but that's the way it works... [1] The 0.8.0-beta1 version number is only for the coordinates of the pom of cassandra-cql that will pull down the dependencies for using cql with cassandra 0.8.0-beta1. If that subtlety helps you understand the versioning I have chosen for the poms, well that is better. It sounds to me like you need to omit the CQL jar entirely then, and not add it to Maven Central except as a different project. -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release Apache Cassandra 0.8.0-beta1 artifacts in Maven Central
On 28 April 2011 15:23, Eric Evans eev...@rackspace.com wrote: On Thu, 2011-04-28 at 06:52 +0100, Stephen Connolly wrote: On 28 April 2011 00:55, Eric Evans eev...@rackspace.com wrote: On Tue, 2011-04-26 at 14:44 +0100, Stephen Connolly wrote: * I have given the CQL driver jar the same version number as everything else, because it is only going to work with the 0.8.0-beta1 jars anyway. Please vote (see http://www.apache.org/foundation/voting.html#ReleaseVotes) +1: Go ahead and release it 0: I have some issues with the release -1: I have something I think merits re-spinning this release -1 Why are we making up a different version number for the client code? 1. because that version of the driver has a hard dependency on the other two jars, and because it is still in tree, therefore it is released in sync. Neither of those is a good reason. 2. I cannot release another 1.0.0 artifact as you cannot overwrite versions in maven central. once you release a version it is released, so unless 0.8.0-beta2 comes with cql 1.0.1 then we are in trouble. You will literally have to increment the cql version for _every single release of the main jars_ or else I will have to make two sets of build targets one which releases cql only and the other which releases everything but cql. That is a messy release process to follow, but if that's what you want... The likelihood that that driver won't receive even a minor bug fix (resulting in version 1.0.1) is low but not non-existent, so whatever the process, it shouldn't absolutely require that driver releases occur when Cassandra releases do. It sounds like that is your problem. from my PoV, there will be many issues releasing (oh why is this fix for cql not in the new release... yes it is... no it isn't... oh, somebody forgot to increment the cql version when doing the release and you are using maven central) unless you do one of several options: * move cql out of tree (so that it is released on its own schedule... we do this @maven for everything... many trees with many independent release schedules) * tie the cql version to the main tree version (what I did) * make the cql version a combo of the main and the cql version (i.e. 1.0.0-0.8.0-beta1) * keep cql in tree but make the build have two targets, 1st for everything but cql, 2nd for only cql (that will be a mess but it is a solution) Unlike the RPC, CQL is meant to be stable. It is a significant feature that you should be able to use the same version of a driver across many versions of Cassandra. This is why the versions must be different, so that you can evaluate each new driver version in the context of how it changed, not (necessarily )how Cassandra changed during some arbitrary release. This version number is all about versioning the information in the __pom__. The pom defines transitive dependencies. You might not rebuild the cql jar at all, but keep redeploying with different poms (each getting their own version number... because we can only use a version number once)... yes that is somewhat wasteful of space on the central repository, but that's the way it works... [1] The 0.8.0-beta1 version number is only for the coordinates of the pom of cassandra-cql that will pull down the dependencies for using cql with cassandra 0.8.0-beta1. If that subtlety helps you understand the versioning I have chosen for the poms, well that is better. When the next release of cassandra hits, there may be a different tree of dependencies for cql, _even_if_you_don't_modify_a_single_cql_class_, in any case there will be different versions of the artifacts in the dependency tree, so, if you like, you need to release a new version of the dependency metadata for cql with every release of cassandra... at least until you remove the dependencies on cassandra core classes and probably the backing thrift transport. [1] we could do a more optimized space version where we have a shim jar (think manifest only) that is very small and pulls in the cassandra deps and the apache-cassandra-cql-1.0.0 jar but that does not really gain us much, we'd still be deploying a cql jar with every release... just not _the_ apache-cql-1.0.0.jar I don't know if driver releases will be made in the time between Cassandra releases, but I suspect that at some point they probably will be. I don't that every driver will need to be released every time that Cassandra does, they probably won't. None of of this should prevent them all from living in the same tree. We can bemoan Maven Central's policy (you can only release a specific version number once and only once), but that does not solve the issue that users want dependencies from a Maven repository, and Maven's architecture will not re-download a release version because of it's central assumption that releases do not change, so even if you could re-release a 1.0.0, anyone who used the old 1.0.0 would not get the new
Re: [VOTE] Release Apache Cassandra 0.8.0-beta1 artifacts in Maven Central
ok well I will see about deleting it from the staging repo, can I get a conditional + 1 on that basis? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 28 Apr 2011 20:31, Eric Evans eev...@rackspace.com wrote: On Thu, 2011-04-28 at 16:44 +0100, Stephen Connolly wrote: Unlike the RPC, CQL is meant to be stable. It is a significant feature that you should be able to use the same version of a driver across many versions of Cassandra. This is why the versions must be different, so that you can evaluate each new driver version in the context of how it changed, not (necessarily )how Cassandra changed during some arbitrary release. This version number is all about versioning the information in the __pom__. The pom defines transitive dependencies. You might not rebuild the cql jar at all, but keep redeploying with different poms (each getting their own version number... because we can only use a version number once)... yes that is somewhat wasteful of space on the central repository, but that's the way it works... [1] The 0.8.0-beta1 version number is only for the coordinates of the pom of cassandra-cql that will pull down the dependencies for using cql with cassandra 0.8.0-beta1. If that subtlety helps you understand the versioning I have chosen for the poms, well that is better. It sounds to me like you need to omit the CQL jar entirely then, and not add it to Maven Central except as a different project. -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release Apache Cassandra 0.8.0-beta1 artifacts in Maven Central
On 28 April 2011 00:55, Eric Evans eev...@rackspace.com wrote: On Tue, 2011-04-26 at 14:44 +0100, Stephen Connolly wrote: * I have given the CQL driver jar the same version number as everything else, because it is only going to work with the 0.8.0-beta1 jars anyway. Please vote (see http://www.apache.org/foundation/voting.html#ReleaseVotes) +1: Go ahead and release it 0: I have some issues with the release -1: I have something I think merits re-spinning this release -1 Why are we making up a different version number for the client code? 1. because that version of the driver has a hard dependency on the other two jars, and because it is still in tree, therefore it is released in sync. 2. I cannot release another 1.0.0 artifact as you cannot overwrite versions in maven central. once you release a version it is released, so unless 0.8.0-beta2 comes with cql 1.0.1 then we are in trouble. You will literally have to increment the cql version for _every single release of the main jars_ or else I will have to make two sets of build targets one which releases cql only and the other which releases everything but cql. That is a messy release process to follow, but if that's what you want... from my PoV, there will be many issues releasing (oh why is this fix for cql not in the new release... yes it is... no it isn't... oh, somebody forgot to increment the cql version when doing the release and you are using maven central) unless you do one of several options: * move cql out of tree (so that it is released on its own schedule... we do this @maven for everything... many trees with many independent release schedules) * tie the cql version to the main tree version (what I did) * make the cql version a combo of the main and the cql version (i.e. 1.0.0-0.8.0-beta1) * keep cql in tree but make the build have two targets, 1st for everything but cql, 2nd for only cql (that will be a mess but it is a solution) We can bemoan Maven Central's policy (you can only release a specific version number once and only once), but that does not solve the issue that users want dependencies from a Maven repository, and Maven's architecture will not re-download a release version because of it's central assumption that releases do not change, so even if you could re-release a 1.0.0, anyone who used the old 1.0.0 would not get the new release (this is why -SNAPSHOTs are different from releases, Maven expects -SNAPSHOTs might change and will check for new versions... but you cannot put -SNAPSHOTs in a release repository) -Stephen -- Eric Evans eev...@rackspace.com
[VOTE] Release Apache Cassandra 0.8.0-beta1 artifacts in Maven Central
Per the Apache release rules, only artifacts which have been voted on can be released. Thus, as I missed the main release vote, I cannot tag onto the end. The artifacts I want to release are: https://repository.apache.org/content/repositories/orgapachecassandra-114/ Notes: * The tar.gz files are different from the main as the -src.tar.gz includes my patch and the -bin.tar.gz has different timestamps on the javadocs (previously I had just been reusing eric's tar.gz's and hacking the patch to no overwrite them... but I think it is better to have the actual source of what is used to generate all the artifacts that make up this staging repo) * I have given the CQL driver jar the same version number as everything else, because it is only going to work with the 0.8.0-beta1 jars anyway. Please vote (see http://www.apache.org/foundation/voting.html#ReleaseVotes) +1: Go ahead and release it 0: I have some issues with the release -1: I have something I think merits re-spinning this release Vote will be open for 72 hours unless the PMC says we can finish quicker and we have met the 3 or more binding +1's minimum -Stephen P.S. I do not have a binding vote at Cassandra, but here is my +1 anyway
Re: [VOTE] Release Apache Cassandra 0.7.5
I've spotted a minor issue with my CASSANDRA-1851 patch... I'll raise a JIRA to address, and I will have to attach a staging repository to this vote for it to be closed successfully (i.e. we are missing the cassandra-parent pom that all the 0.7.5 poms inherit from) On 22 April 2011 18:17, Sylvain Lebresne slebre...@apache.org wrote: I propose the following artifacts for release as 0.7.5. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1095960 Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-113/org/apache/cassandra/apache-cassandra/0.7.5/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-113 The artifacts as well as a debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours. [1]: goo.gl/1i0Ce (CHANGES.txt) [2]: goo.gl/cLaqR (NEWS.txt)
Re: [VOTE] Release Apache Cassandra 0.7.5
https://repository.apache.org/content/repositories/orgapachecassandra-115/ contains the missing artifact for deployment to maven central https://issues.apache.org/jira/browse/CASSANDRA-2562 will patch 0.7.x to ensure this works going forward. Unless anyone objects, please consider the 115 staging repo as appended onto this vote -Stephen On 26 April 2011 14:45, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I've spotted a minor issue with my CASSANDRA-1851 patch... I'll raise a JIRA to address, and I will have to attach a staging repository to this vote for it to be closed successfully (i.e. we are missing the cassandra-parent pom that all the 0.7.5 poms inherit from) On 22 April 2011 18:17, Sylvain Lebresne slebre...@apache.org wrote: I propose the following artifacts for release as 0.7.5. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1095960 Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-113/org/apache/cassandra/apache-cassandra/0.7.5/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-113 The artifacts as well as a debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours. [1]: goo.gl/1i0Ce (CHANGES.txt) [2]: goo.gl/cLaqR (NEWS.txt)
Re: Why is the CQL jar versioned independently?
so will cql get its own tree from which releases well be cut, or will it get released always at the same time? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 26 Apr 2011 22:19, Eric Evans eev...@rackspace.com wrote: On Tue, 2011-04-26 at 13:31 +0100, Stephen Connolly wrote: From what I can see, the intent is to always release lock-step in sync with cassandra, in which case the version number should be the cassandra version number... unless you are implying that this is CQL version 1.0.0 and there may be a future time when you could have CQL version 2.0.0 with a different incompatible syntax... CQL client versioning does *not* move in lock-step with either Cassandra or the CQL specification (though if you adhere to semver.org for both the spec and the library then *major* versions will effectively move in lock-step). -- Eric Evans eev...@rackspace.com
Re: [VOTE RESULTS] was: [VOTE] Apache Cassandra 0.8.0-beta1 (take #2)
yep will be so doing, but those poms have issues, such as depending transitively on a slf4j implementation also ranges are non reproducable, so it will be a specific version - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 25 Apr 2011 21:44, Jake Farrell jfarr...@apache.org wrote: Stephen As part of the 0.6.1 thrift release the libthrift and libfb303 are now available in the apache repo ( http://repo1.maven.org/maven2/org/apache/thrift/). Can you reference these jars rather than deploying a second set to the m2 repo in the cassandra deps folder. I looked for a pom or ivy.xml to submit a patch against but couldnt find it in the trunk, is this checked in? - Jake dependency groupIdorg.apache.thrift/groupId artifactIdlibthrift/artifactId version[0.6.1,)/version /dependency On Apr 23, 2011, at 5:46 AM, Stephen Connolly wrote: I am in the process of ensuring that the 0.8 poms are correct. it is taking slightly longer than I expected as I got pulled into firefighting with aws/skynet and my wife has banned me from the computer this weekend! I'll call a vote for them early next week (needs a vote under apache rules, that will take 3 days unless the cassandra pmc is happy to go with a shorter vote) short version: expect poms in central on friday - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 23 Apr 2011 07:33, Tristan Tarrant tristan.tarr...@gmail.com wrote:
[VOTE] Promote extra-enforcer-rules out of the sandbox and release version 1.0-alpha-1
Hi Mojo developers, I'd like to promote the extra-enforcer-rules subproject out of the sandbox and release version 1.0-alpha-1 This sub-project is designed to allow for hosting of custom rules for the enforcer plugin. The project site is deployed at: http://mojo.codehaus.org/extra-enforcer-rules/ and 1.0-alpha-1-SNAPSHOT has been deployed to Codehaus's Snapshot repository: https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/mojo/extra-enforcer-rules/1.0-alpha-1-SNAPSHOT/extra-enforcer-rules-1.0-alpha-1-20110419.091232-3.jar +!: yeah 0: wha -1: nahh 72 hours lazy consensus OR more than five +1's whichever comes first! [*] -Stephen [*] I'm being cheeky with my attempt to release faster so i'm setting the bar a little higher for a fast vote, and anyway we don't have any really hard and fast rules for votes at Mojo ;-)
Re: [VOTE] Promote extra-enforcer-rules out of the sandbox and release version 1.0-alpha-1
Sorry never mind the spam... stupid GMail autocomplete! On 19 April 2011 10:22, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi Mojo developers, I'd like to promote the extra-enforcer-rules subproject out of the sandbox and release version 1.0-alpha-1 This sub-project is designed to allow for hosting of custom rules for the enforcer plugin. The project site is deployed at: http://mojo.codehaus.org/extra-enforcer-rules/ and 1.0-alpha-1-SNAPSHOT has been deployed to Codehaus's Snapshot repository: https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/mojo/extra-enforcer-rules/1.0-alpha-1-SNAPSHOT/extra-enforcer-rules-1.0-alpha-1-20110419.091232-3.jar +!: yeah 0: wha -1: nahh 72 hours lazy consensus OR more than five +1's whichever comes first! [*] -Stephen [*] I'm being cheeky with my attempt to release faster so i'm setting the bar a little higher for a fast vote, and anyway we don't have any really hard and fast rules for votes at Mojo ;-)
Re: [VOTE] Apache Cassandra 0.8.0-beta1
FYI: http://www.apache.org/foundation/voting.html#ReleaseVotes quoteReleases may not be vetoed/quote On 19 April 2011 13:42, Shotaro Kamio kamios...@gmail.com wrote: -1, I'd like to make 0.8 to include the fix for CASSANDRA-2406. The fix is committed to the 0.8 branch lately. I'll wait for beta2. Regards, Shotaro On Tue, Apr 19, 2011 at 10:42 AM, Jonathan Ellis jbel...@gmail.com wrote: CASSANDRA-2448 means https://issues.apache.org/jira/browse/CASSANDRA-2448 On Mon, Apr 18, 2011 at 8:32 PM, Huang Stanley wenlien1...@gmail.com wrote: +1 I'm looking forward to 0.8 :-) And one question about 0.8 beta1, I saw an item in the change log: * remove nodetool loadbalance (CASSANDRA-2448) any reason? any alternative solution to keep data balance? regards, Stanley Huang regards, Stanley Huang On Tue, Apr 19, 2011 at 5:28 AM, Gary Dusbabek gdusba...@gmail.com wrote: +1 On Mon, Apr 18, 2011 at 13:44, Eric Evans eev...@rackspace.com wrote: OK. Here are artifacts for a proposed 0.8 beta1 release. You will note the addition of three new artifacts, cql-1.0.0.tar.gz, txcql-1.0.0.tar.gz and apache-cassandra-cql-1.0.0.jar. These are language drivers for CQL; Be sure to include them in your review. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1094668 0.8.0-beta1 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours, longer if needed. Thanks! -- Eric Evans eev...@rackspace.com -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
[ANN] Maven ANT Tasks 2.1.3 Released
The Maven team is pleased to announce the release of Maven ANT Tasks, version 2.1.3. The Mavent Ant Tasks allow several of Maven's artifact handling features to be used from within an Ant build. These include: Dependency management - including transitive dependencies, scope recognition and SNAPSHOT handling Artifact deployment - deployment to a Maven repository (file integrated, other with extensions) POM processing - for reading and writing a Maven 2 pom.xml file The ANT tasks can be downloaded from http://maven.apache.org/ant-tasks/download.html Release Notes - Maven 2.x Ant Tasks - Version 2.1.3 ** Bug * [MANTTASKS-218] - cacheDependencyRefs is ignored when pulling dependencies from a pom defined in the build.xml Enjoy, -The Maven team
Re: Release Manager Volunteers?
Why should you limit to just one volunteer? The idea is that the procedure in http://wiki.apache.org/cassandra/HowToPublishReleases should be followable by any Cassandra committer. I would propose that the release manager is the person who steps up to run the release for that specific release. If it is just one person always making releases then that becomes a SPOF... better to have more than one and round-robin it, or have one do the stable releases and the other do the new releases... I'd volunteer as well only I don't have commit access... (I have access to publish to maven central on behalf of cassandra, but that's a whole other story) -Stephen On 13 April 2011 22:43, Sylvain Lebresne sylv...@datastax.com wrote: That is probably a mistake I'm going to regret soon enough, but since it doesn't sound I'm stealing the idea to anyone I'm volunteering. -- Sylvain On Mon, Apr 11, 2011 at 11:43 PM, Eric Evans eev...@racklabs.com wrote: On Mon, 2011-04-11 at 16:40 -0500, Eric Evans wrote: The amount of time I'm able to commit to Cassandra going forward is uncertain, plus, it wouldn't hurt give someone else a turn, or to have some redundancy here. Do we have any volunteers? The requirements are: * Committer * Gluten for punishment That would be glutton of course, release management is 100% gluten-free. -- Eric Evans eev...@racklabs.com
RE: CASSANDRA-1851 and other stuff
I have created http://wiki.apache.org/cassandra/HowToPublishToMavenCentral which is involved in relation to https://issues.apache.org/jira/browse/CASSANDRA-1851 If some committers could give feedback. I'd like to get the patch to land in 0.7 quickly so I can produce an updated patch for 0.8 before the 11th deadline -Stephen
Added a wiki page for people having issues building...
http://wiki.apache.org/cassandra/HowToBuild A number of people have had issues building Cassandra... Things like: 1. Not using ANT 1.8 or newer (you might get away with 1.7 though but 1.6 is a no go) 2. Not using JDK 1.6 or newer (you might get part of the way with 1.5 as that is the required minimum for Maven ANT tasks, but Cassandra depends on 1.6 classes... trying to build with GCJ ain't going to work) 3. Not having an internet connection to download the dependencies initially. 4. Not having proxy settings configured for ANT. -Stephen
Status of deploy to maven central patch
Just an FYI. I have the required fixes for Maven ANT Tasks in place: http://jira.codehaus.org/browse/MANTTASKS-217 http://jira.codehaus.org/browse/MANTTASKS-211 http://jira.codehaus.org/browse/MANTTASKS-210 I plan to run a release of Maven ANT Tasks early next week. Once the release is place I should have the patches for 0.8.x and 0.7.x shortly after. Once the 0.7.x patch has landed it would be great if we could spin a 0.7.5 just to trial the patches to verify that they do actually result in a valid release getting pushed all the way to central, and to verify that I have the wiki page for making the release in place -Stephen
Re: [VOTE] 0.7.4
OK. I've got internet access and pushed the artifacts to central. should be available in 4-6 hours On 13 March 2011 22:38, Stephen Connolly stephen.alan.conno...@gmail.comwrote: On 12 March 2011 00:50, Eric Evans eev...@rackspace.com wrote: It's that time again. I propose the following for release as 0.7.4. What say you? SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1080811 0.7.4 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. [1]: http://goo.gl/ZwACq (CHANGES.txt) [2]: http://goo.gl/Ib28x (NEWS.txt) -- Eric Evans eev...@rackspace.com OK, here's the artifacts to tag onto the vote for promotion to central: https://repository.apache.org/content/repositories/orgapachecassandra-005/ *Description:* apache cassandra 0.7.4 take #1 *Details:* The following artifacts have been staged to the org.apache.cassandra-005https://repository.apache.org/content/repositories/orgapachecassandra-005 repository. archetype-catalog.xmlhttps://repository.apache.org/content/repositories/orgapachecassandra-005/archetype-catalog.xml apache-cassandra-0.7.4-src.tar.gzhttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/apache-cassandra/0.7.4/apache-cassandra-0.7.4-src.tar.gz apache-cassandra-0.7.4-src.tar.gz.aschttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/apache-cassandra/0.7.4/apache-cassandra-0.7.4-src.tar.gz.asc apache-cassandra-0.7.4-bin.tar.gzhttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/apache-cassandra/0.7.4/apache-cassandra-0.7.4-bin.tar.gz apache-cassandra-0.7.4.pom.aschttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/apache-cassandra/0.7.4/apache-cassandra-0.7.4.pom.asc apache-cassandra-0.7.4-bin.tar.gz.aschttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/apache-cassandra/0.7.4/apache-cassandra-0.7.4-bin.tar.gz.asc apache-cassandra-0.7.4.pomhttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/apache-cassandra/0.7.4/apache-cassandra-0.7.4.pom cassandra-all-0.7.4.jar.aschttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/cassandra-all/0.7.4/cassandra-all-0.7.4.jar.asc cassandra-all-0.7.4-sources.jar.aschttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/cassandra-all/0.7.4/cassandra-all-0.7.4-sources.jar.asc cassandra-all-0.7.4.jarhttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/cassandra-all/0.7.4/cassandra-all-0.7.4.jar cassandra-all-0.7.4-javadoc.jarhttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/cassandra-all/0.7.4/cassandra-all-0.7.4-javadoc.jar cassandra-all-0.7.4-sources.jarhttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/cassandra-all/0.7.4/cassandra-all-0.7.4-sources.jar cassandra-all-0.7.4.pom.aschttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/cassandra-all/0.7.4/cassandra-all-0.7.4.pom.asc cassandra-all-0.7.4.pomhttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/cassandra-all/0.7.4/cassandra-all-0.7.4.pom cassandra-all-0.7.4-javadoc.jar.aschttps://repository.apache.org/content/repositories/orgapachecassandra-005/org/apache/cassandra/cassandra-all/0.7.4/cassandra-all-0.7.4-javadoc.jar.asc Eric, I am on holidays for the next week and may not have internet access. If this vote succeeds on take #1 can you please promote the staging repository? Steps are as follows: 1. open https://repository.apache.org 2. login (link on top right hand side of the screen... it'a apache LDAP username and password) 3. Select Staging Repositories on the Left hand side menu 4. Tick the checkbox for the apache cassandra repo 5. Click the Release link (above the list of repos in the main body) 6. Fill in the comment for the promotion notification email (I normally just go with apache cassandra 0.7.4 take #1 for example) 7. Close your browser you are done! If you need a take#2 then it will have to wait until after the 22nd and I'll probably miss a vote to tag onto so i'll have to run a separate vote but I'm sure people will just have to accept the delays then! Thanks -Stephen
Re: Code coverage Jenkins Job
Hmm failure due to some difference when the code is instrumented... points to some threading issue that might need to be looked at. In any case, in order to get Code Coverage to work consistently, it would be good if somebody could apply https://issues.apache.org/jira/browse/CASSANDRA-2298 Thanks -Stephen On 9 March 2011 09:27, Stephen Connolly stephen.alan.conno...@gmail.comwrote: FYI, I am trialling enabling the Cassandra Coverage job I created on Jenkins. I'm setting the schedule to daily. We'll see how it works out -Stephen
Re: [VOTE] 0.7.3 take #2
I'll see if I can stage while hanging around Dublin Airport after that data roaming costs are prohibitive -Stephen On 1 March 2011 19:32, Eric Evans eev...@rackspace.com wrote: Here goes attempt #2 of 0.7.3 (see http://goo.gl/Y1l7n for background); I propose the following for release as 0.7.3. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7.3@r1075977 0.7.3 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. Thanks. [1]: http://goo.gl/hX02M (CHANGES.txt) [2]: http://goo.gl/HXlNH (NEWS.txt) -- Eric Evans eev...@rackspace.com
Re: [VOTE] 0.7.3 take #2
On 1 March 2011 19:32, Eric Evans eev...@rackspace.com wrote: Here goes attempt #2 of 0.7.3 (see http://goo.gl/Y1l7n for background); I propose the following for release as 0.7.3. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7.3@r1075977 0.7.3 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. Thanks. [1]: http://goo.gl/hX02M (CHANGES.txt) [2]: http://goo.gl/HXlNH (NEWS.txt) -- Eric Evans eev...@rackspace.com Artifacts staged for promotion to maven central repository: https://repository.apache.org/content/repositories/orgapachecassandra-001/ *Description:* apache cassandra 0.7.3 take #2 *Details:* The following artifacts have been staged to the org.apache.cassandra-001 (u:stephenc)https://repository.apache.org/content/repositories/orgapachecassandra-001 repository. archetype-catalog.xmlhttps://repository.apache.org/content/repositories/orgapachecassandra-001/archetype-catalog.xml apache-cassandra-0.7.3-src.tar.gz.aschttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/apache-cassandra/0.7.3/apache-cassandra-0.7.3-src.tar.gz.asc apache-cassandra-0.7.3.pom.aschttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/apache-cassandra/0.7.3/apache-cassandra-0.7.3.pom.asc apache-cassandra-0.7.3-bin.tar.gz.aschttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/apache-cassandra/0.7.3/apache-cassandra-0.7.3-bin.tar.gz.asc apache-cassandra-0.7.3.pomhttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/apache-cassandra/0.7.3/apache-cassandra-0.7.3.pom apache-cassandra-0.7.3-src.tar.gzhttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/apache-cassandra/0.7.3/apache-cassandra-0.7.3-src.tar.gz apache-cassandra-0.7.3-bin.tar.gzhttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/apache-cassandra/0.7.3/apache-cassandra-0.7.3-bin.tar.gz cassandra-all-0.7.3.pomhttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3.pom cassandra-all-0.7.3-javadoc.jar.aschttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3-javadoc.jar.asc cassandra-all-0.7.3.jar.aschttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3.jar.asc cassandra-all-0.7.3.jarhttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3.jar cassandra-all-0.7.3-sources.jarhttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3-sources.jar cassandra-all-0.7.3-javadoc.jarhttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3-javadoc.jar cassandra-all-0.7.3-sources.jar.aschttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3-sources.jar.asc cassandra-all-0.7.3.pom.aschttps://repository.apache.org/content/repositories/orgapachecassandra-001/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3.pom.asc
Re: [VOTE] 0.7.3
ok, if you are respinning i can restage for central tomorrow. but i am traveling on wed so it would be better to stage on tuesday (ie have the respin tonight so a can stage tomorrow) i will be working on extending maven-ant-tasks on the plane to add the features required to generate simple poms for the cassandra artifacts. once i have that ready and get it through a release vote @maven i will be able to provide a patch that will enable all cassandra committers can stage to maven central. should simplify eric's releasing (artifacts will be in the staging repo automatically, with gpg signatures) respins will just be a second staging repo, and you just promote the successful vote - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 28 Feb 2011 23:31, Jonathan Ellis jbel...@gmail.com wrote:
Re: [VOTE] 0.7.3
On 25 February 2011 21:09, Eric Evans eev...@rackspace.com wrote: Shall we? I propose the following for release as 0.7.3. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1074693 0.7.3 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. Thanks. [1]: http://goo.gl/0CykW (CHANGES.txt) [2]: http://goo.gl/9NNKv (NEWS.txt) -- Eric Evans eev...@rackspace.com Artifacts staged for promotion to maven central at https://repository.apache.org/content/repositories/orgapachecassandra-057/ *Description:* apache cassandra 0.7.3 take #1 *Details:* The following artifacts have been staged to the org.apache.cassandra-057 (u:stephenc)https://repository.apache.org/content/repositories/orgapachecassandra-057 repository. apache-cassandra-0.7.3-src.tar.gz.aschttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/apache-cassandra/0.7.3/apache-cassandra-0.7.3-src.tar.gz.asc apache-cassandra-0.7.3.pom.aschttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/apache-cassandra/0.7.3/apache-cassandra-0.7.3.pom.asc apache-cassandra-0.7.3-bin.tar.gz.aschttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/apache-cassandra/0.7.3/apache-cassandra-0.7.3-bin.tar.gz.asc apache-cassandra-0.7.3.pomhttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/apache-cassandra/0.7.3/apache-cassandra-0.7.3.pom apache-cassandra-0.7.3-src.tar.gzhttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/apache-cassandra/0.7.3/apache-cassandra-0.7.3-src.tar.gz apache-cassandra-0.7.3-bin.tar.gzhttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/apache-cassandra/0.7.3/apache-cassandra-0.7.3-bin.tar.gz cassandra-all-0.7.3.pomhttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3.pom cassandra-all-0.7.3-javadoc.jar.aschttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3-javadoc.jar.asc cassandra-all-0.7.3.jar.aschttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3.jar.asc cassandra-all-0.7.3.jarhttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3.jar cassandra-all-0.7.3-sources.jarhttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3-sources.jar cassandra-all-0.7.3-javadoc.jarhttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3-javadoc.jar cassandra-all-0.7.3-sources.jar.aschttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3-sources.jar.asc cassandra-all-0.7.3.pom.aschttps://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/cassandra-all/0.7.3/cassandra-all-0.7.3.pom.asc
Re: [VOTE] 0.7.2
On 15 February 2011 22:18, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 15 February 2011 21:57, Eric Evans eev...@rackspace.com wrote: CASSANDRA-2165[1] is troublesome enough to warrant a new release. I propose the following for 0.7.2. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7.2@r1071063 Minor niggle, that revision has the build.xml with base.version=0.7.1 Ahhh sorry my fault you changed the branch url I'm re-staging the artifacts in repository.apache.org -Stephen 0.7.2 artifacts: http://people.apache.org/~eevans The delta here is pretty small, so if no one objects, we can reduce the voting period to 24 hours. [1]: https://issues.apache.org/jira/browse/CASSANDRA-2165 [2]: http://goo.gl/iI7U2 (CHANGES.txt) [3]: http://goo.gl/b2dCq (NEWS.txt) -- Eric Evans eev...@rackspace.com
Re: [VOTE] 0.7.2
On 15 February 2011 22:19, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 15 February 2011 22:18, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 15 February 2011 21:57, Eric Evans eev...@rackspace.com wrote: CASSANDRA-2165[1] is troublesome enough to warrant a new release. I propose the following for 0.7.2. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7.2@r1071063 Minor niggle, that revision has the build.xml with base.version=0.7.1 Ahhh sorry my fault you changed the branch url But the changed url is still having the wrong base.version! -Stephen I'm re-staging the artifacts in repository.apache.org -Stephen 0.7.2 artifacts: http://people.apache.org/~eevans The delta here is pretty small, so if no one objects, we can reduce the voting period to 24 hours. [1]: https://issues.apache.org/jira/browse/CASSANDRA-2165 [2]: http://goo.gl/iI7U2 (CHANGES.txt) [3]: http://goo.gl/b2dCq (NEWS.txt) -- Eric Evans eev...@rackspace.com
Re: [VOTE] 0.7.2
On 15 February 2011 21:57, Eric Evans eev...@rackspace.com wrote: CASSANDRA-2165[1] is troublesome enough to warrant a new release. I propose the following for 0.7.2. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7.2@r1071063 0.7.2 artifacts: http://people.apache.org/~eevans The delta here is pretty small, so if no one objects, we can reduce the voting period to 24 hours. [1]: https://issues.apache.org/jira/browse/CASSANDRA-2165 [2]: http://goo.gl/iI7U2 (CHANGES.txt) [3]: http://goo.gl/b2dCq (NEWS.txt) -- Eric Evans eev...@rackspace.com https://repository.apache.org/content/repositories/orgapachecassandra-012/ Description: apache cassandra 0.7.2 take 1 Details: The following artifacts have been staged to the org.apache.cassandra-012 (u:stephenc) repository. apache-cassandra-0.7.2.pom.asc apache-cassandra-0.7.2.pom apache-cassandra-0.7.2-src.tar.gz apache-cassandra-0.7.2-bin.tar.gz apache-cassandra-0.7.2-bin.tar.gz.asc apache-cassandra-0.7.2-src.tar.gz.asc cassandra-all-0.7.2.jar.asc cassandra-all-0.7.2.pom.asc cassandra-all-0.7.2-javadoc.jar cassandra-all-0.7.2.jar cassandra-all-0.7.2.pom cassandra-all-0.7.2-sources.jar.asc cassandra-all-0.7.2-sources.jar cassandra-all-0.7.2-javadoc.jar.asc
Re: [VOTE RESULT] was: [VOTE] 0.7.1 (what are we at now, 4?)
I'll publish to maven central - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 14 Feb 2011 19:20, Eric Evans eev...@rackspace.com wrote:
Re: [VOTE] 0.7.1 (what are we at now, 4?)
On 10 February 2011 18:49, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I'll restage central artifacts by tommorrow morning. hoping this is the last take - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 10 Feb 2011 17:50, Eric Evans eev...@rackspace.com wrote: I propose the following for release as 0.7.1. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1069461 0.7.1 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. [1]: http://goo.gl/5VAPP (CHANGES.txt) [2]: http://goo.gl/C9M5W (NEWS.txt) [3]: http://goo.gl/8dZUr -- Eric Evans eev...@rackspace.com Here are the artifacts staged for publishing to repository.apache.org (which will be synced to maven central) https://repository.apache.org/content/repositories/orgapachecassandra-056/ Description: apache cassandra 0.7.1 take 4 Details: The following artifacts have been staged to the org.apache.cassandra-056 repository. apache-cassandra-0.7.1-src.tar.gz apache-cassandra-0.7.1-bin.tar.gz.asc apache-cassandra-0.7.1.pom.asc apache-cassandra-0.7.1.pom apache-cassandra-0.7.1-bin.tar.gz apache-cassandra-0.7.1-src.tar.gz.asc cassandra-all-0.7.1.pom cassandra-all-0.7.1-sources.jar cassandra-all-0.7.1-sources.jar.asc cassandra-all-0.7.1.pom.asc cassandra-all-0.7.1.jar cassandra-all-0.7.1-javadoc.jar cassandra-all-0.7.1.jar.asc cassandra-all-0.7.1-javadoc.jar.asc https://repository.apache.org/content/repositories/orgapachecassandra-081/ Description: apache cassandra 0.7.1 Details: The following artifacts have been staged to the org.apache.cassandra-081 (u:stephenc) repository. cassandra-javautils-0.7.1.pom cassandra-javautils-0.7.1-sources.jar.asc cassandra-javautils-0.7.1.jar cassandra-javautils-0.7.1-sources.jar cassandra-javautils-0.7.1.jar.asc cassandra-javautils-0.7.1-javadoc.jar.asc cassandra-javautils-0.7.1.pom.asc cassandra-javautils-0.7.1-javadoc.jar -Stephen
Re: [VOTE] 0.7.1 (what are we at now, 4?)
I'll restage central artifacts by tommorrow morning. hoping this is the last take - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 10 Feb 2011 17:50, Eric Evans eev...@rackspace.com wrote: I propose the following for release as 0.7.1. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1069461 0.7.1 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. [1]: http://goo.gl/5VAPP (CHANGES.txt) [2]: http://goo.gl/C9M5W (NEWS.txt) [3]: http://goo.gl/8dZUr -- Eric Evans eev...@rackspace.com
Re: [VOTE] 0.7.1 (3 times the charm?)
On 4 February 2011 19:40, Eric Evans eev...@rackspace.com wrote: Lather. Rinse. Repeat. Ya'll know the drill. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1067260 0.7.1 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. [1]: http://goo.gl/axEK0 (CHANGES.txt) [2]: http://goo.gl/66yGY (NEWS.txt) -- Eric Evans eev...@rackspace.com Here are the artifacts staged for publishing to repository.apache.org (which will be synced to maven central) https://repository.apache.org/content/repositories/orgapachecassandra-036/ Description: apache cassandra 0.7.1 take 3 Details: The following artifacts have been staged to the org.apache.cassandra-036 (u:stephenc) repository. apache-cassandra-0.7.1-src.tar.gz apache-cassandra-0.7.1-bin.tar.gz.asc apache-cassandra-0.7.1.pom.asc apache-cassandra-0.7.1.pom apache-cassandra-0.7.1-bin.tar.gz apache-cassandra-0.7.1-src.tar.gz.asc cassandra-all-0.7.1.pom cassandra-all-0.7.1-sources.jar cassandra-all-0.7.1-sources.jar.asc cassandra-all-0.7.1.pom.asc cassandra-all-0.7.1.jar cassandra-all-0.7.1-javadoc.jar cassandra-all-0.7.1.jar.asc cassandra-all-0.7.1-javadoc.jar.asc https://repository.apache.org/content/repositories/orgapachecassandra-081/ Description: apache cassandra 0.7.1 Details: The following artifacts have been staged to the org.apache.cassandra-081 (u:stephenc) repository. cassandra-javautils-0.7.1.pom cassandra-javautils-0.7.1-sources.jar.asc cassandra-javautils-0.7.1.jar cassandra-javautils-0.7.1-sources.jar cassandra-javautils-0.7.1.jar.asc cassandra-javautils-0.7.1-javadoc.jar.asc cassandra-javautils-0.7.1.pom.asc cassandra-javautils-0.7.1-javadoc.jar -Stephen
Re: [VOTE] 0.7.1 (attempt #2)
I've re-staged the main artifacts. The javautils stuff did not have any changes so I've left that staging repository as is from take #1 https://repository.apache.org/content/repositories/orgapachecassandra-015/ Description: apache cassandra 0.7.1 take #2 Details: The following artifacts have been staged to the org.apache.cassandra-015 (u:stephenc, a:78.16.195.88) repository. apache-cassandra-0.7.1-src.tar.gz apache-cassandra-0.7.1-bin.tar.gz.asc apache-cassandra-0.7.1.pom.asc apache-cassandra-0.7.1.pom apache-cassandra-0.7.1-bin.tar.gz apache-cassandra-0.7.1-src.tar.gz.asc cassandra-all-0.7.1.pom cassandra-all-0.7.1-sources.jar cassandra-all-0.7.1-sources.jar.asc cassandra-all-0.7.1.pom.asc cassandra-all-0.7.1.jar cassandra-all-0.7.1-javadoc.jar cassandra-all-0.7.1.jar.asc cassandra-all-0.7.1-javadoc.jar.asc https://repository.apache.org/content/repositories/orgapachecassandra-081/ Description: apache cassandra 0.7.1 Details: The following artifacts have been staged to the org.apache.cassandra-081 (u:stephenc, a:92.251.255.13) repository. cassandra-javautils-0.7.1.pom cassandra-javautils-0.7.1-sources.jar.asc cassandra-javautils-0.7.1.jar cassandra-javautils-0.7.1-sources.jar cassandra-javautils-0.7.1.jar.asc cassandra-javautils-0.7.1-javadoc.jar.asc cassandra-javautils-0.7.1.pom.asc cassandra-javautils-0.7.1-javadoc.jar On 28 January 2011 20:32, Eric Evans eev...@rackspace.com wrote: CASSANDRA-2058[1] has landed in 0.7, so let's give this another shot. I propose the following for release as 0.7.1. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1064845 0.7.1 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. [1]: https://issues.apache.org/jira/browse/CASSANDRA-2058 [2]: http://goo.gl/5Tafg (CHANGES.txt) [3]: http://goo.gl/PkreZ (NEWS.txt) -- Eric Evans eev...@rackspace.com
Re: Simple Compression Idea
On 31 January 2011 04:41, David G. Boney dbon...@semanticartifacts.com wrote: I propose a simple idea for compression using a compressed string datatype. The compressed string datatype could be implemented for column family keys by creating a compressed string ordered partitioner. The compressed string ordered partitioner works by decompressing the string and then applying an ordered partitioner for strings to the decompressed string. The hash based partitioner would be used with the compressed string without any modification. The compressed string datatype could be implemented for column keys by creating a compressed string comparator. A compressed string comparator would work by decompressing the string and then applying a string comparator. The compressed string datatype could be implemented for column values. The compressed string datatype would be an internal datatype for Cassandra. The compressed string would be converted to a string before returning the value to a client. I suppose you could also have an option of passing the compressed form back to the client if the client wanted it that way. I propose using an adaptive arithmetic coding compressor. This type of compression can be done a byte at a time. It will build a compression model only on the string that is presented, a byte at a time. See the below papers. Moffat, Alistair, Radford M. Neal, Ian H. Witten, (1998), Arithmetic Coding Revisited, ACM Trans. on Info. Systems, Vol. 16, No. 3, pp. 256-294. Witten, Ian H., Radford M. Neal, John G. Cleary, (1987), Arithmetic Coding for Data Compression, Communications of the ACM, Vol. 30, No. 6, pp. 520-540. It has been reported that arithmetic coding based compression applied to text can get compression ratios of up to 2.2 bits per character. Assuming you only get 4 bits per character because of short strings. This would be a 50% compression of text data, including keys and column names. Many applications would benefit. It should speed up the overall operation of Cassandra because you would be moving significantly less data through the system. I have not read those papers but how do they and their reported compressions apply to the unicode characters that java strings are stored as? -Stephen This would provide a compression option that could be implemented without any redesign to the internal structure of Cassandra except for the a new partitioner class, a new comparator class, a new datatype class, and the compression class. - Sincerely, David G. Boney dbon...@semanticartifacts.com http://www.semanticartifacts.com
Re: [VOTE] 0.7.1 (attempt #2)
I'm getting Bad Gateway The proxy server received an invalid response from an upstream server. From repository.apache.org. So the Maven central artifacts will probably be staged tomorrow AM (as my wife will kill me if I waste Sunday working on this! and she'd be right too!) ;-) -Stephen On 28 January 2011 20:34, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I'll drop and restage the artifacts for maven central when I get a chance - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 28 Jan 2011 20:30, Eric Evans eev...@rackspace.com wrote: CASSANDRA-2058[1] has landed in 0.7, so let's give this another shot. I propose the following for release as 0.7.1. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1064845 0.7.1 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. [1]: https://issues.apache.org/jira/browse/CASSANDRA-2058 [2]: http://goo.gl/5Tafg (CHANGES.txt) [3]: http://goo.gl/PkreZ (NEWS.txt) -- Eric Evans eev...@rackspace.com
[PMC VOTE] Approve use of Cassandra mark by mojo.codehaus.org
Since there does not seem to be any desire to accept CASSANDRA-1997 Can the PMC vote to approve the use of the Cassandra mark by the mojo.codehaus.org project for the Cassandra Maven Plugin +1 Approve 0 don't care -1 Veto 72 hours PMC votes only -Stephen
Re: [PMC VOTE] Approve use of Cassandra mark by mojo.codehaus.org
adding shane. shane, am I being overly cautious or have we more fun here ps I am only on the maven pmc, so I cannot follow if you jump to priv...@cassandra.apache.org - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 28 Jan 2011 19:21, Eric Evans eev...@rackspace.com wrote: On Fri, 2011-01-28 at 19:07 +, Stephen Connolly wrote: Since there does not seem to be any desire to accept CASSANDRA-1997 Can the PMC vote to approve the use of the Cassandra mark by the mojo.codehaus.org project for the Cassandra Maven Plugin I don't understand why you'd need permission. Help me to understand why this is necessary. If it is necessary, then I suspect there are other cases ongoing where we need to defend our mark. +1 Approve 0 don't care -1 Veto I'm not going to vote on something I don't understand. -- Eric Evans eev...@rackspace.com
Re: [VOTE] 0.7.1 (attempt #2)
I'll drop and restage the artifacts for maven central when I get a chance - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 28 Jan 2011 20:30, Eric Evans eev...@rackspace.com wrote: CASSANDRA-2058[1] has landed in 0.7, so let's give this another shot. I propose the following for release as 0.7.1. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1064845 0.7.1 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. [1]: https://issues.apache.org/jira/browse/CASSANDRA-2058 [2]: http://goo.gl/5Tafg (CHANGES.txt) [3]: http://goo.gl/PkreZ (NEWS.txt) -- Eric Evans eev...@rackspace.com
Re: [VOTE] 0.7.1
seemingly this very reason is why tomcat-maven-plugin is moving from mojo to tomcat - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 27 Jan 2011 17:11, Eric Evans eev...@rackspace.com wrote:
Re: [VOTE] 0.7.1
Artifacts staged at https://repository.apache.org/content/repositories/orgapachecassandra-080/ https://repository.apache.org/content/repositories/orgapachecassandra-081/ -Stephen On 25 January 2011 23:00, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I'll stage artifacts in central tomorrow AM GMT On 25 January 2011 23:01, Eric Evans eev...@rackspace.com wrote: Shall we? I propose the following artifacts for release as 0.7.1. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1063491 0.7.1 artifacts: http://people.apache.org/~eevans The will remain open for 72 hours, (longer if need be). [1]: http://goo.gl/4cJkq (CHANGES.txt) [2]: http://goo.gl/SBGPA (NEWS.txt) -- Eric Evans eev...@rackspace.com
Re: [VOTE] 0.7.1
Attached, for the record only, is the diff I used to stage the
artifacts for publishing to Central.
Note that this diff is not ready for application to the code base. I
am still working on some things. Specifically it looks like I may
have to push a new release of maven-ant-tasks as I think I found a NPE
in generating a pom with a parent pom. (And I want to use a parent pom
so that we don't have dependency version details scattered all over
the build.xml)
-Stephen
On 26 January 2011 11:43, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Artifacts staged at
https://repository.apache.org/content/repositories/orgapachecassandra-080/
https://repository.apache.org/content/repositories/orgapachecassandra-081/
-Stephen
On 25 January 2011 23:00, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
I'll stage artifacts in central tomorrow AM GMT
On 25 January 2011 23:01, Eric Evans eev...@rackspace.com wrote:
Shall we? I propose the following artifacts for release as 0.7.1.
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1063491
0.7.1 artifacts: http://people.apache.org/~eevans
The will remain open for 72 hours, (longer if need be).
[1]: http://goo.gl/4cJkq (CHANGES.txt)
[2]: http://goo.gl/SBGPA (NEWS.txt)
--
Eric Evans
eev...@rackspace.com
Index: build.xml
===
--- build.xml (revision 1063491)
+++ build.xml (working copy)
@@ -59,6 +59,10 @@
property name=maven-ant-tasks.version value=2.1.1 /
property name=maven-ant-tasks.url
value=http://repo2.maven.org/maven2/org/apache/maven/maven-ant-tasks; /
+!-- details of how and which Maven repository we publish to --
+property name=maven.version value=2.2.1 /
+property name=maven-repository-url value=https://repository.apache.org/service/local/staging/deploy/maven2; /
+property name=maven-repository-id value=apache.releases.https /
!-- http://cobertura.sourceforge.net/ --
property name=cobertura.build.dir value=${build.dir}/cobertura/
@@ -221,6 +225,24 @@
/copy
/target
+macrodef name=deploy
+ attribute name=pomFile/
+ attribute name=file/
+ attribute name=classifier default=/
+ attribute name=packaging default=jar/
+ sequential
+artifact:mvn mavenVersion=${maven.version} fork=true
+ arg value=org.apache.maven.plugins:maven-gpg-plugin:1.1:sign-and-deploy-file /
+ arg value=-Durl=${maven-repository-url} /
+ arg value=-DrepositoryId=${maven-repository-id} /
+ arg value=-DpomFile=@{pomFile} /
+ arg value=-Dfile=@{file} /
+ arg value=-Dclassifier=@{classifier} /
+ arg value=-Dpackaging=@{packaging} /
+/artifact:mvn
+ /sequential
+/macrodef
+
!--
Generate avro code
--
@@ -362,6 +384,133 @@
/jar
/target
+!--
+The javadoc-jar target makes cassandra-javadoc.jar output required for publishing to Maven central repository.
+--
+target name=javadoc-jar depends=javadoc description=Assemble Cassandra JavaDoc JAR file
+ jar jarfile=${build.dir}/${final.name}-javadoc.jar
+ basedir=${javadoc.dir}/
+/target
+
+!--
+The sources-jar target makes cassandra-sources.jar output required for publishing to Maven central repository.
+--
+target name=sources-jar depends=init,avro-generate description=Assemble Cassandra Sources JAR file
+ jar jarfile=${build.dir}/${final.name}-sources.jar
+ fileset dir=${build.src.java} defaultexcludes=yes
+include name=org/apache/**/*.java/
+ /fileset
+ fileset dir=${interface.thrift.gen-java} defaultexcludes=yes
+include name=org/apache/**/*.java/
+ /fileset
+ fileset dir=${interface.avro.dir} defaultexcludes=yes
+include name=org/apache/**/*.java/
+ /fileset
+ /jar
+/target
+
+target name=scm-info description=Determines the current Subversion URL with peg revision
+ exec executable=svn dir=${basedir} output=${build.dir}/svn-info.xml
+arg line=info --xml/
+ /exec
+ xmlproperty file=${build.dir}/svn-info.xml collapseAttributes=true prefix=svn keepRoot=false/
+ echo file=${build.dir}/scm.properties
+connection=scm:svn:${svn.entry.url}@${svn.entry.commit.revision}
+developerConnection=scm:svn:${svn.entry.url}@${svn.entry.commit.revision}
+url=${svn.entry.url}?pathrev=${svn.entry.commit.revision}
+ /echo
+ replace file=${build.dir}/scm.properties
+replacefilter token=connection=scm:svn:https: value=connection=scm:svn:http:/
+replacefilter token=Connection=scm:svn:http: value=Connection=scm:svn:https:/
+replacefilter token=url=${svn.entry.repository.root} value=url=http://svn.apache.org/viewvc/
+ /replace
+ property file=${build.dir}/scm.properties prefix=scm/
+/target
+
+target name=all-pom depends=init
Re: [VOTE] 0.7.1
if 0.7.1 is being respun can we get cassandra-1997 added to contrib so that I can release it at the same time if you don't want it as part of cassandra, it would be good to know as I would either need approval to use the cassandra mark if hosting outside cassandra (I can't host it at maven as we are only hosting core plugins) or it would require a name that is completely non obvious making the user experience worse. (the maven pmc are currently having fun with clarifying what we are supposed to do to protect the maven mark, so I know a little... a dangerous thing ;-) ) - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 27 Jan 2011 04:05, Jonathan Ellis jbel...@gmail.com wrote:
Re: [VOTE] 0.7.1
I'll stage artifacts in central tomorrow AM GMT On 25 January 2011 23:01, Eric Evans eev...@rackspace.com wrote: Shall we? I propose the following artifacts for release as 0.7.1. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1063491 0.7.1 artifacts: http://people.apache.org/~eevans The will remain open for 72 hours, (longer if need be). [1]: http://goo.gl/4cJkq (CHANGES.txt) [2]: http://goo.gl/SBGPA (NEWS.txt) -- Eric Evans eev...@rackspace.com
Replacing ivy with maven-ant-tasks
Is this something that people are OK with? It will result in the version details being specified from the build.xml and not a separate ivy.xml Which branch shall I target first... My preference is to target 0.7 and then when the modularization takes place in trunk/0.8 it will be on top of the maven-ant-tasks changes. If everyone is OK I'll create a JIRA against Core with fixVersion 0.7 and add my patch there. -Stephen
Re: Replacing ivy with maven-ant-tasks
On 18 January 2011 14:30, Eric Evans eev...@rackspace.com wrote: On Tue, 2011-01-18 at 13:13 +, Stephen Connolly wrote: Is this something that people are OK with? Why? What are the advantages? 1. It will make deploying to central easier (as ivy does not deploy correct poms, and maven-ant-tasks can generate correct poms) 2. _You_ seemed to think it would be better keeping all the version information in build.xml rather than in a separate file 3. You seemed to think it might be a good idea when you saw the mavebn-ant-tasks stuff for deploying to central There's probably some more but those are the main drivers from my perspective. Note Maven-Ant-Tasks is not Maven... it provides essentially the same functionality as ivy only targetted exclusively at Maven repositories... (which are the only really repository format (other than p2) to take off) -Stephen
Fwd: Nexus: Promotion Completed.
-- Forwarded message -- From: Nexus Repository Manager ne...@repository.apache.org Date: 10 January 2011 07:57 Subject: Nexus: Promotion Completed. To: Stephen Connolly stephen.alan.conno...@gmail.com Description: apache-cassandra:0.7.0 Details: The following artifacts have been promoted to the Releases repository. apache-cassandra-0.7.0-bin.tar.gz.asc apache-cassandra-0.7.0.pom apache-cassandra-0.7.0.pom.asc apache-cassandra-0.7.0-src.tar.gz apache-cassandra-0.7.0-bin.tar.gz apache-cassandra-0.7.0-src.tar.gz.asc cassandra-all-0.7.0-javadoc.jar cassandra-all-0.7.0-javadoc.jar.asc cassandra-all-0.7.0.jar cassandra-all-0.7.0.pom cassandra-all-0.7.0-sources.jar.asc cassandra-all-0.7.0.jar.asc cassandra-all-0.7.0-sources.jar cassandra-all-0.7.0.pom.asc cassandra-javautils-0.7.0.jar cassandra-javautils-0.7.0.pom cassandra-javautils-0.7.0-javadoc.jar cassandra-javautils-0.7.0-sources.jar cassandra-javautils-0.7.0-sources.jar.asc cassandra-javautils-0.7.0.jar.asc cassandra-javautils-0.7.0.pom.asc cassandra-javautils-0.7.0-javadoc.jar.asc
Re: [VOTE RESULTS] was: [VOTE] 7.0
I'll push the staged artifacts to central... they'll be there in about 1 to 6 hours - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 10 Jan 2011 00:19, Eric Evans eev...@rackspace.com wrote: On Thu, 2011-01-06 at 11:17 -0600, Eric Evans wrote: SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0@r1055934 0.7.0 artifacts: http://people.apache.org/~eevans The vote will be open for at least 72 hours. I count 4 binding +1s, 5 others, and no -1s. The vote passes. An ASF press release is scheduled for tomorrow so I'll get the artifacts up tonight, but I'm going to hold off on the announcement until tomorrow. -- Eric Evans eev...@rackspace.com
[RESULT] [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
Results +1: Gary, Jonathan, Brandon I will promote the staging repositories and the sync to central should kick in within an hour or so. Is there any standard set of lists I should announce this on? -Stephen On 2 January 2011 20:50, Stephen Connolly stephen.alan.conno...@gmail.comwrote: As I am not a cassandra committer I'd rather do the promotion with a vote. There are two staging repositories: https://repository.apache.org/content/repositories/orgapachecassandra-065/ Which contains the dependencies which are not available in the maven central repository (libthrift and avro... actually these are slightly tweaked as jars with both .java and .class files can cause problems for people when compiling code, so I have stripped out the .java files and rebuilt) The second staging repository is: https://repository.apache.org/content/repositories/orgapachecassandra-064/ This contains the actual cassandra jars. I have given these the GAV of org.apache.cassandra:cassandra-all:0.7.0-rc4 for two reasons: 1. There will be eventually cassandra-thrift-server, cassandra-core, cassandra-thrift-client, etc [not committing to how they will be split out, but the point is that they will be split out] so a -all.jar makes most naming sense in this case 2. Also don't want to conflict with the riptano GAV coordinates as there is a 0.7.0-rc4 already. Attached is the patch I am using to publish the cassandra jars: Vote will be open for 72 hours and will proceed by lazy consensus. -Stephen
Re: [RESULT] [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
still waiting for the sync to complete, then I'll post the announce - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 5 Jan 2011 23:09, Brandon Williams dri...@gmail.com wrote: On Wed, Jan 5, 2011 at 3:45 PM, Jonathan Ellis jbel...@gmail.com wrote: cassandra user and hector user lists are probably most interested. client-dev would be good too. -Brandon
Re: [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
(battery on laptop died) ... move to a consolidated set of dependencies. Also did you forget to vote? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2011 14:16, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
Re: [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
voting options are: +1 - publish 0 - don't care -1 - there's a problem with the poms - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 2 Jan 2011 20:50, Stephen Connolly stephen.alan.conno...@gmail.com wrote: As I am not a cassandra committer I'd rather do the promotion with a vote. There are two staging repositories: https://repository.apache.org/content/repositories/orgapachecassandra-065/ Which contains the dependencies which are not available in the maven central repository (libthrift and avro... actually these are slightly tweaked as jars with both .java and .class files can cause problems for people when compiling code, so I have stripped out the .java files and rebuilt) The second staging repository is: https://repository.apache.org/content/repositories/orgapachecassandra-064/ This contains the actual cassandra jars. I have given these the GAV of org.apache.cassandra:cassandra-all:0.7.0-rc4 for two reasons: 1. There will be eventually cassandra-thrift-server, cassandra-core, cassandra-thrift-client, etc [not committing to how they will be split out, but the point is that they will be split out] so a -all.jar makes most naming sense in this case 2. Also don't want to conflict with the riptano GAV coordinates as there is a 0.7.0-rc4 already. Attached is the patch I am using to publish the cassandra jars: Vote will be open for 72 hours and will proceed by lazy consensus. -Stephen
Re: Consolidating ivy.xml, was: [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
maven-ant-tasks would allow what you want, no install of maven (unless publishing to central, in which case the install is hidden in ~/m2) and all dependency info in the build.xml I'll work on a patch to show how that would look like (on trunk, leave 0.7.0 as it is, less risk) - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2011 15:01, Gary Dusbabek gdusba...@gmail.com wrote:
Re: [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
sort of... you'll actually stage the artifacts and vote for three release and the staged artifacts at the same time. the patch is my diff... as a record of what I have done... not for committing yet. when I have a patch for commuting I'll raise a jira and attach it... or hey if you want to make me a commiter it would be easier to work the changes in a branch and merge... it's a pity infra don't create a sandbox in repo/asf which is write able for all apache commuters - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2011 19:11, Eric Evans eev...@rackspace.com wrote: So, for clarification, you're holding this vote for the 7.0 rc4 artifacts because the build.xml changes are as-of-yet uncommitted (and too late for 7.0). Once our build system has caught up, this is something we'll be able to do after a successful release vote, and using the same artifacts. Is that right? Also, the `pom' target in your patch fails for me with: https://gist.github.com/b9a2214e274e5700a995 Thanks again for working on this Stephen. On Sun, 2011-01-02 at 20:50 +, Stephen Connolly wrote: As I am not a cassandra committer I'd rather do the promotion with a vote. There are two staging repositories: https://repository.apache.org/content/repositories/orgapachecassandra-065/ Which contains the dependencies which are not available in the maven central repository (libthrift and avro... actually these are slightly tweaked as jars with both .java and .class files can cause problems for people when compiling code, so I have stripped out the .java files and rebuilt) The second staging repository is: https://repository.apache.org/content/repositories/orgapachecassandra-064/ This contains the actual cassandra jars. I have given these the GAV of org.apache.cassandra:cassandra-all:0.7.0-rc4 for two reasons: 1. There will be eventually cassandra-thrift-server, cassandra-core, cassandra-thrift-client, etc [not committing to how they will be split out, but the point is that they will be split out] so a -all.jar makes most naming sense in this case 2. Also don't want to conflict with the riptano GAV coordinates as there is a 0.7.0-rc4 already. Attached is the patch I am using to publish the cassandra jars: Vote will be open for 72 hours and will proceed by lazy consensus. -Stephen -- Eric Evans eev...@rackspace.com
[VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
As I am not a cassandra committer I'd rather do the promotion with a vote.
There are two staging repositories:
https://repository.apache.org/content/repositories/orgapachecassandra-065/
Which contains the dependencies which are not available in the maven central
repository (libthrift and avro... actually these are slightly tweaked as
jars with both .java and .class files can cause problems for people when
compiling code, so I have stripped out the .java files and rebuilt)
The second staging repository is:
https://repository.apache.org/content/repositories/orgapachecassandra-064/
This contains the actual cassandra jars.
I have given these the GAV of org.apache.cassandra:cassandra-all:0.7.0-rc4
for two reasons:
1. There will be eventually cassandra-thrift-server, cassandra-core,
cassandra-thrift-client, etc [not committing to how they will be split out,
but the point is that they will be split out] so a -all.jar makes most
naming sense in this case
2. Also don't want to conflict with the riptano GAV coordinates as there is
a 0.7.0-rc4 already.
Attached is the patch I am using to publish the cassandra jars:
Vote will be open for 72 hours and will proceed by lazy consensus.
-Stephen
Index: build.xml
===
--- build.xml (revision 1053977)
+++ build.xml (working copy)
@@ -18,7 +18,8 @@
~ under the License.
--
project basedir=. default=build name=apache-cassandra
- xmlns:ivy=antlib:org.apache.ivy.ant
+ xmlns:ivy=antlib:org.apache.ivy.ant
+ xmlns:artifact=antlib:org.apache.maven.artifact.ant
property environment=env/
property file=build.properties /
property name=debuglevel value=source,lines,vars/
@@ -57,6 +58,11 @@
property name=ivy.version value=2.1.0 /
property name=ivy.url
value=http://repo2.maven.org/maven2/org/apache/ivy/ivy; /
+property name=mavenanttasks.version value=2.1.1 /
+property name=mavenanttasks.url
+ value=http://repo2.maven.org/maven2/org/apache/maven/maven-ant-tasks; /
+property name=maven-repository-url value=https://repository.apache.org/service/local/staging/deploy/maven2; /
+property name=maven-repository-id value=apache.releases.https /
!-- http://cobertura.sourceforge.net/ --
property name=cobertura.build.dir value=${build.dir}/cobertura/
@@ -70,6 +76,10 @@
available file=${build.dir}/ivy-${ivy.version}.jar /
/condition
+condition property=mavenanttasks.jar.exists
+ available file=${build.dir}/maven-ant-tasks-${mavenanttasks.version}.jar /
+/condition
+
condition property=is.source.artifact
available file=${build.src.java} type=dir /
/condition
@@ -83,6 +93,7 @@
/fileset
pathelement location=${build.dir}/ivy-${ivy.version}.jar/
/path
+path id=maven-ant-tasks.classpath path=${build.dir}/maven-ant-tasks-${mavenanttasks.version}.jar /
path id=cassandra.classpath
pathelement location=${cobertura.classes.dir}/
pathelement location=${build.classes}/
@@ -164,6 +175,21 @@
property name=ivy.initialized value=true/
/target
+target name=maven-ant-tasks-download unless=mavenanttasks.jar.exists
+ echoDownloading Maven ANT Tasks.../echo
+ mkdir dir=${build.dir} /
+ get src=${mavenanttasks.url}/${mavenanttasks.version}/maven-ant-tasks-${mavenanttasks.version}.jar
+ dest=${build.dir}/maven-ant-tasks-${mavenanttasks.version}.jar usetimestamp=true /
+/target
+
+target name=maven-ant-tasks-init depends=maven-ant-tasks-download unless=mavenanttasks.initialized
+ mkdir dir=${build.dir.lib}/
+ typedef resource=org/apache/maven/artifact/ant/antlib.xml
+ uri=antlib:org.apache.maven.artifact.ant
+ classpathref=maven-ant-tasks.classpath /
+ property name=mavenanttasks.initialized value=true/
+/target
+
target name=ivy-retrieve-build depends=ivy-init
ivy:retrieve type=jar,source sync=true
pattern=${build.dir.lib}/[type]s/[artifact]-[revision].[ext] /
@@ -310,6 +336,94 @@
/jar
/target
+target name=javadoc-jar depends=javadoc description=Assemble Cassandra JavaDoc JAR file
+ jar jarfile=${build.dir}/${final.name}-javadoc.jar
+ basedir=${javadoc.dir}/
+/target
+
+target name=sources-jar depends=init,avro-generate description=Assemble Cassandra Sources JAR file
+ jar jarfile=${build.dir}/${final.name}-sources.jar
+ fileset dir=${build.src.java} defaultexcludes=yes
+include name=org/apache/**/*.java/
+ /fileset
+ fileset dir=${interface.thrift.gen-java} defaultexcludes=yes
+include name=org/apache/**/*.java/
+ /fileset
+ fileset dir=${interface.avro.dir} defaultexcludes=yes
+include name=org/apache/**/*.java/
+ /fileset
+ /jar
+/target
+target name=pom depends=init,maven-ant-tasks-init description=Create Maven POM file
+
Re: interest in creating a cassandra-gossip library?
I've pinged peter, as the only builds of his that I know of are for the company I'm working for (until march) and he used to work for... Hopefully he has some public examples - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 29 Dec 2010 15:00, Eric Evans eev...@rackspace.com wrote: On Tue, 2010-12-28 at 22:25 +, Stephen Connolly wrote: In my experience, one big source tree leads to unwanted module dependencies, and can lead to circular module dependencies, which render the modulization moot anyway... (note I am not saying to go to m_v__ as a build tool, just to keep module source code in separate trees so that intra-module dependencies can be controlled... Of course I believe that other build tool is good at helping, but if you've ever seen one of peter reilly's ANT builds you'll know it can be done easily and beautifully in ANT... Admittedly he is on the ANT pmc ;-) ) Can you link to an example of one of these? -- Eric Evans eev...@rackspace.com
Re: interest in creating a cassandra-gossip library?
Is there a specific reason to avoid modularizing the source folders if we are modularizing the jars? In my experience, one big source tree leads to unwanted module dependencies, and can lead to circular module dependencies, which render the modulization moot anyway... (note I am not saying to go to m_v__ as a build tool, just to keep module source code in separate trees so that intra-module dependencies can be controlled... Of course I believe that other build tool is good at helping, but if you've ever seen one of peter reilly's ANT builds you'll know it can be done easily and beautifully in ANT... Admittedly he is on the ANT pmc ;-) ) - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 28 Dec 2010 20:17, Ryan King r...@twitter.com wrote: On Wed, Dec 22, 2010 at 11:07 AM, matthew hawthorne mhawtho...@gmail.com wrote: hello, I'm starting a project at my day job to deploy a gossip protocol implementation. part of my initial work is to evaluate existing implementations. being loosely familiar with Cassandra, I read http://wiki.apache.org/cassandra/ArchitectureGossip and have looked over the related code a bit. is there interest in breaking out the gossip-related portions of Cassandra into a library that could be reused by other projects? I work on a team that is ready and willing to contribute heavily. we'd just need some guidance as to how to structure the Cassandra subcomponent(s) and properly integrate them with the builds, tests, etc. I think breaking gossip out could be very valuable. Gossip is a somewhat under-understood and under-tested part of Cassandra. Isolating it could help both of those situations. Ideally we'd not change the normal build procedure for cassandra, but add a new target for building a gossip library. here are a few examples of functionality we're looking to add: 1) hierarchical state - our use case is cross data center gossip, where we don't want every node in the 2 clusters communicating, but do want a node from cluster1 to send a summary of the cluster's state to cluster2, and vice versa. essentially I'm talking about rolling up the state of multiple nodes into a single virtual node I'd be interested in seeing the analysis here. There are some challenging problems with having only one host do something in a gossip based system. 2) mutual authentication - nodes verifying the identity of other nodes before gossipping 3) encryption - encrypted traffic, especially for the cross data center case any opinions on this? thanks in advance for any feedback! -ryan
Handy script to check the contents of jar files to see if the classes are the same despite being different compilers
#!/bin/bash if [ $# != 2 ] ; then echo Syntax: $0 name1.jar name2.jar exit fi if diff $1 $2 ; then echo Files are identical exit 0 fi work=$(mktemp -d) mkdir -p $work/a mkdir -p $work/b cwd=$(pwd) cd $work/a unzip $cwd/$1 | sort $work/a.list cd $work/b unzip $cwd/$2 | sort $work/b.list cd $work if ! diff a.list b.list diff.list ; then echo Contents; echo =; cat diff.list; echo ; echo Contents are different summary; fi for class in $(find a -name \*.class | sed -e s:^\\a/::;s:\\.class$::;s:/:.:g); do javap -c -classpath a $class a.javap; javap -c -classpath b $class b.javap; if ! diff a.javap b.javap diff.javap ; then echo $class; echo =; cat diff.javap; echo ; echo $class summary; fi; done if [ -f summary ]; then echo Summary echo === cat summary else echo File contents are identical fi cd $cwd rm -rf $work
Re: Handy script to check the contents of jar files to see if the classes are the same despite being different compilers
Can be helpful with CASSANDRA-1888 On 21 December 2010 22:41, Stephen Connolly stephen.alan.conno...@gmail.com wrote: #!/bin/bash if [ $# != 2 ] ; then echo Syntax: $0 name1.jar name2.jar exit fi if diff $1 $2 ; then echo Files are identical exit 0 fi work=$(mktemp -d) mkdir -p $work/a mkdir -p $work/b cwd=$(pwd) cd $work/a unzip $cwd/$1 | sort $work/a.list cd $work/b unzip $cwd/$2 | sort $work/b.list cd $work if ! diff a.list b.list diff.list ; then echo Contents; echo =; cat diff.list; echo ; echo Contents are different summary; fi for class in $(find a -name \*.class | sed -e s:^\\a/::;s:\\.class$::;s:/:.:g); do javap -c -classpath a $class a.javap; javap -c -classpath b $class b.javap; if ! diff a.javap b.javap diff.javap ; then echo $class; echo =; cat diff.javap; echo ; echo $class summary; fi; done if [ -f summary ]; then echo Summary echo === cat summary else echo File contents are identical fi cd $cwd rm -rf $work
Getting artifacts into maven central (INFRA-3318)
I have created https://issues.apache.org/jira/browse/INFRA-3318 Can somebody on the Cassandra PMC comment on the issue and say that it's fine for me to be driving the process Thanks, -Stephen Apache Maven PMC
Re: Getting artifacts into maven central (INFRA-3318)
On 21 December 2010 23:42, Brandon Williams dri...@gmail.com wrote: On Tue, Dec 21, 2010 at 5:39 PM, Stephen Connolly steph...@apache.org wrote: I have created https://issues.apache.org/jira/browse/INFRA-3318 Can somebody on the Cassandra PMC comment on the issue and say that it's fine for me to be driving the process I gave it a +1 -Brandon thanks
Re: Any chance of getting cassandra releases published to repo1.maven.org?
OK, to keep everyone up to date, I have been working on getting the one non-ASL licensed dependency that is not in central into central (high-scale-lib)... Should have that sorted soon enough, at which point my plan is as follows. Get the 0.7.0 release in central in its current uber-jar form... it would be nice to have this split into the client libraries... but at this point in time that seems to be seen as too much risk for 0.7.0, so I'll not fight that. Any ASL licensed dependencies not already in central will be pushed to central under the org.apache.cassandra groupId (i.e. libthrift, etc) The cassandra project is already redistributing these artifacts, so there is no harm in doing that via central. Then try and help in splitting out the next version into separate jars and try and help the upstream ASL licensed projects to get into central (I note that libthrift is supposed to be making progress) This may require me to get my hands really dirty and try and help hadoop get a release out ;-) -Stephen On 14 December 2010 23:52, Eric Evans eev...@rackspace.com wrote: On Tue, 2010-12-14 at 19:39 +, Stephen Connolly wrote: Well one piece of evidence is that the ivy.xml does not look to have been kept in sync with the binaries in the lib directory... That is my argument for not keeping binaries in lib folders... No, the contents of lib/ are runtime dependencies; It's what gets rolled into release artifacts. Ivy is used to retrieve build dependencies. -- Eric Evans eev...@rackspace.com
Re: Any chance of getting cassandra releases published to repo1.maven.org?
On 13 December 2010 16:26, Eric Evans eev...@rackspace.com wrote: On Mon, 2010-12-13 at 05:51 +, Stephen Connolly wrote: The binaries in the lib folder, is there any objection to piling them down from the maven central repository via ivy if they are available on the maven central repository? We're obligated to redistribute these jars according to the terms of the respective licenses. That could mean including a copy of the license, attribution, or both. We've stopped short of pulling these down with ivy because it's a dynamic process, with no programmatic way of obtaining terms, attribution, etc. For those that are not on central, can I assume that legal has ok'ed they're redistribution if they are not originating at apache? We're complying with the terms of redistribution in binary form, to the best of my knowledge. OK, on that basis the beast way to go is to push the same jars that are being redistributed into central under the o.a.c groupId... it amounts to the same as you are doing currently... but I may look into putting in place some automation to consolidate duplicate jars -- Eric Evans eev...@rackspace.com
Re: Any chance of getting cassandra releases published to repo1.maven.org?
On 13 December 2010 19:06, Eric Evans eev...@rackspace.com wrote: On Mon, 2010-12-13 at 17:12 +, Stephen Connolly wrote: OK, on that basis the beast way to go is to push the same jars that are being redistributed into central under the o.a.c groupId... it amounts to the same as you are doing currently... but I may look into putting in place some automation to consolidate duplicate jars Can you elaborate more on this? Are you saying that we'd continue to maintain the contents of lib/ in svn, and publish the jars to our groupId in the repo at release time? Or, do you mean that we'd maintain the canonical list jars in the repo and retrieve them at build time? What I mean is that we'd use ivy (or maven ant tasks if you are not opposed to it... but it doesn't really matter which) to pull down what we think is the matching version in SVN, and then compare the md5 or sha1 of the lib version with the repo version. If the checksum matches, then we point the pom at the repo version, otherwise we redist the SVN lib version in o.a.c... so as long as you keep pulling down versions that are in central the pom will correctly point to the repo version (without munging up the GAV coordinates) and the Maven/Gradle/Ivy/Grapes world will be happy. -- Eric Evans eev...@rackspace.com
Any chance of getting cassandra releases published to repo1.maven.org?
Hi, I was looking to see if I could find the cassandra jars on the maven central repository (repo1.maven.org) but I see that they are not there (http://repo1.maven.org/maven2/org/apache/cassandra - 404 not found) So I had a quick search of the mailing lists and this was what I found: http://markmail.org/message/7e73pborosogjlo5?q=list:org%2Eapache%2Eincubator%2Ecassandra-dev+maven I will hereby put my head above the parapet: I am willing to support mvn users, respond to the jira tickets they generate, and send patches to the committers. Just to be clear, I do not want to change your build from ant to maven. I just want to see the artifacts published to the maven central repository so that people using maven/gradle/etc (i.e. all the build tools that pull jars from the maven central repository) can easily use cassandra. Do you want my help, and if so where do you want me to start? -Stephen
Re: Any chance of getting cassandra releases published to repo1.maven.org?
The binaries in the lib folder, is there any objection to piling them down from the maven central repository via ivy if they are available on the maven central repository? For those that are not on central, can I assume that legal has ok'ed they're redistribution if they are not originating at apache? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 13 Dec 2010 05:19, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Are official releases made from svn or from git? And how exactly do you run your release process? E.g. do you cut the tag and run from the tag, or do you run the build from trunk and then make the tag? I'm hoping the first as it will make generating the pom easier (as the pom is supposed to have the scm section for the build origin, but I can always just use a peg revision on trunk if you cut builds direct from trunk and tag after the fact) - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 13 Dec 2010 03:38, Eric Evans eev...@rackspace.com wrote: On Sun, 2010-12-12 at 23:44 +, Stephen Connolly wrote: Hi, I was looking to see if I could find the cassandra jars on the maven central repository (repo1.maven.org) but I see that they are not there (http://repo1.maven.org/maven2/org/apache/cassandra - 404 not found) So I had a quick search of the mailing lists and this was what I found: http://markmail.org/message/7e73pborosogjlo5?q=list:org%2Eapache%2Eincubator%2Ecassandra-dev+maven I will hereby put my head above the parapet: I am willing to support mvn users, respond to the jira tickets they generate, and send patches to the committers. Just to be clear, I do not want to change your build from ant to maven. I just want to see the artifacts published to the maven central repository so that people using maven/gradle/etc (i.e. all the build tools that pull jars from the maven central repository) can easily use cassandra. Do you want my help, and if so where do you want me to start? So first off, you should know that Riptano hosts a maven repo. It's not an official project resource, and it's not hosted on Apache infrastructure, but it should do the job. http://mvn.riptano.com/content/repositories/riptano If that's not Good Enough and you want Official support, then personally I'd be agreeable to a solution that published directly from ant, or at the very least, generated a pom.xml in the build target, and removed it on clean. I have little faith at this point that maintaining a pom.xml is going to work for us. -- Eric Evans eev...@rackspace.com
