[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.
cassandra user and hector user lists are probably most interested. On Wed, Jan 5, 2011 at 3:37 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: 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 -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
Re: [RESULT] [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
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: [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.
Stephen, Please lay down some mvn/ant wisdom on us... Is there a way to link/include the dependency logic from the 'pom' target and the ivy.xml file we use? It would be great if the dependency information could be consolidated in one place. Great work, btw. Gary. On Sun, Jan 2, 2011 at 14: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: [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: [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
+1. I didn't test the artifacts, but any effort to get mvn artifacts published that doesn't force mvn on the entire project gets my vote. Gary. On Sun, Jan 2, 2011 at 14: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
Consolidating ivy.xml, was: [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
Voted and moved this discussion to a different thread. My goal (other devs please chime in because I'm interested) would be to still rely on ant for building and generating a pom, without the requirement to explicitly install maven. If we could get rid of ivy.xml by having the relevant details in build.xml that would be excellent! Getting rid of lib is another discussion. We've been down that path already and it sounds like you're aware of the licensing concerns. Gary. On Mon, Jan 3, 2011 at 08:43, Stephen Connolly stephen.alan.conno...@gmail.com wrote: (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: Consolidating ivy.xml, was: [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
On Mon, Jan 3, 2011 at 9:01 AM, Gary Dusbabek gdusba...@gmail.com wrote: Voted and moved this discussion to a different thread. My goal (other devs please chime in because I'm interested) would be to still rely on ant for building and generating a pom, without the requirement to explicitly install maven. If we could get rid of ivy.xml by having the relevant details in build.xml that would be excellent! This would be my goal too. -Brandon
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.
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
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
+
