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 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.
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) 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 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 > 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" 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" 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 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 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" > 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 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" wrote:
Re: [VOTE] Publish cassandra-0.7.0-rc4 to maven central repository.
+1 On Mon, Jan 3, 2011 at 8:52 AM, Gary Dusbabek 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 > 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.
+1 On Sun, Jan 2, 2011 at 2:50 PM, 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.
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" 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 >
