You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Stephen Connolly <st...@gmail.com> on 2011/01/02 21:50:03 UTC
[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
Re: [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
Posted by Brandon Williams <dr...@gmail.com>.
+1
On Sun, Jan 2, 2011 at 2:50 PM, Stephen Connolly <
stephen.alan.connolly@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.
Posted by Stephen Connolly <st...@gmail.com>.
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" <st...@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: [RESULT] [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
Posted by Stephen Connolly <st...@gmail.com>.
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" <dr...@gmail.com> wrote:
> On Wed, Jan 5, 2011 at 3:45 PM, Jonathan Ellis <jb...@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.
Posted by Brandon Williams <dr...@gmail.com>.
On Wed, Jan 5, 2011 at 3:45 PM, Jonathan Ellis <jb...@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.
Posted by Jonathan Ellis <jb...@gmail.com>.
cassandra user and hector user lists are probably most interested.
On Wed, Jan 5, 2011 at 3:37 PM, Stephen Connolly
<st...@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
> <st...@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
>>
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com
[RESULT] [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
Posted by Stephen Connolly <st...@gmail.com>.
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
<st...@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.
Posted by Stephen Connolly <st...@gmail.com>.
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" <ee...@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 +0000, 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
> eevans@rackspace.com
>
Re: [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
Posted by Eric Evans <ee...@rackspace.com>.
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 +0000, 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
eevans@rackspace.com
Re: [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
Posted by Stephen Connolly <st...@gmail.com>.
(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" <st...@gmail.com>
wrote:
Re: [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
Posted by Stephen Connolly <st...@gmail.com>.
Yep I'd ditch ivy and the lib folder for maven-ant-tasks...
After battling with ivy for ages I have come to the conclusion that it's
trying to be too smart... [when trying to generate pom files] but you should
not confuse how you have done things...
the runtime dependencies of cassandra are all in lib... not pulled from
ivy... it would be easy to grab the effective classpath from the pom task
and thereby remove the need for the lib folder... could probably knock
something up to pull down the licenses referenced from the poms of the
specific versions specified in that pom task
something like (note this is untested)
<target name="make-lib" depends="pom">
<artifact:dependencies filesetId="dependency.fileset" pomRefId="all-pom" />
<copy todir="${basedir}/lib">
<fileset refid="dependency.fileset" />
<!-- This mapper strips off all leading directory information -->
<mapper type="flatten" />
</copy>
</target>
in the interim while we have the lib/pom duality I have gone and found all
the dependencies and verified that the versions I have specified are
equivalent at the bytecode level to the ones I have specified... as long as
you have the actual dependencies in SVN there will be issues!
Note that the reason the dependencies are in SVN is so that you can be sure
of the license information...
Now I would like to update some of the deps in lib to the same version of
the jars that I am referencing... but I can appreciate that the 0.7.0
release is a higher priority... so I am fine being pragmatic and doing the
verification _by hand_ at this point in time... but I hope that in the
future we can move to
On 3 January 2011 14:00, Gary Dusbabek <gd...@gmail.com> wrote:
> 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
> <st...@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.
Posted by Gary Dusbabek <gd...@gmail.com>.
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
<st...@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.
Posted by Jonathan Ellis <jb...@gmail.com>.
+1
On Mon, Jan 3, 2011 at 8:52 AM, Gary Dusbabek <gd...@gmail.com> wrote:
> +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
> <st...@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
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com
Re: [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
Posted by Gary Dusbabek <gd...@gmail.com>.
+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
<st...@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