Another question, under which jira component should I create the issue to hold my patch?
- 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 +0000, 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 >
