incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Nine <>
Subject Thoughts on best practices to begin maven releases
Date Sat, 19 Jun 2010 23:37:10 GMT
Hi all,
  I spent some time on IRC and have volunteered to maintain the maven
releases for Cassandra.  Our company uses maven heavily, and I found getting
up and running with Cassandra/Pelops etc was more time consuming as a user
than I feel it should be.  I personally feel that if Cassandra is published
via the main maven repo, this will encourage the deployment of other client
binaries to the main repository and make the community a bit easier to join
as a maven user.

I've downloaded the 6.2 source from svn, and have experimented with adding
pom generation from the ant build file via ivy.  Unfortunately the ant
ivy:makepom task seems too inadequate to perform the tasks that will be
required to publish a working dependency of cassandra.  Can anyone give me a
quick rundown of what attempts have been made to add pom and maven
functionality to the releases?  I don't want to go down the path of
something that been attempted but found too cumbersome to properly maintain.
 If I can get this done in time, I'd like to get it in to the 0.6.3 build if
everyone is keen.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message