Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Subject: Re: Any chance of getting cassandra releases published to
 repo1.maven.org?
From: Eric Evans <eevans@rackspace.com>
To: dev@cassandra.apache.org
In-Reply-To: <m2tyigbavi.fsf@dhcp-01.borud.no>
References: <AANLkTinuwqJUSgyhjeyLQbU-ADSmSopHU-D5P5_Bf0F5@mail.gmail.com>
	 <1292211622.7542.564.camel@erebus.lan>  <m2tyigbavi.fsf@dhcp-01.borud.no>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 14 Dec 2010 17:44:41 -0600
Message-ID: <1292370281.7542.620.camel@erebus.lan>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2010-12-14 at 17:02 +0100, Bjorn Borud wrote:
> Eric Evans <eevans@rackspace.com> writes:
> 
> > I have little faith at this point that maintaining a pom.xml is
> going to
> > work for us.
> 
> why?  (if you have answered this question before I apologize) 

This has come up a lot, the list archives tell the story, but the
executive summary is:

1. Someone contributes a pom.xml and promises to maintain it.
2. They don't.
3. It becomes horribly out of date and is removed.
4. Goto 1

-- 
Eric Evans
eevans@rackspace.com