Mailing-List: contact cassandra-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Subject: Re: Announcing 0.3.0
From: Eric Evans <eevans@racklabs.com>
To: cassandra-dev@incubator.apache.org
In-Reply-To: <7f951de50907201652h361a592fx5d1bdc30cedcd43c@mail.gmail.com>
References: <1248119848.27703.71.camel@achilles>
	 <4d0f9db0907201419w3b106e71x7b8fa76f26ef6394@mail.gmail.com>
	 <1248129373.27703.77.camel@achilles>
	 <7f951de50907201652h361a592fx5d1bdc30cedcd43c@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Organization: Racklabs
Date: Tue, 21 Jul 2009 10:54:29 -0500
Message-Id: <1248191669.27703.101.camel@achilles>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit

On Tue, 2009-07-21 at 01:52 +0200, Carl Byström wrote:
> On Tue, Jul 21, 2009 at 12:36 AM, Eric Evans <eevans@rackspace.com> wrote:

[ ... ]

> > I know next to nothing about maven, is this something that requires the
> > distribution to include a pom.xml? Put another way, 0.3.0 is immutable
> > at this point, so is this something that can still be done or would it
> > require another release?
> 
> I just ran a modified version of Hiram's Maven patch on 0.3.0-final (
> https://issues.apache.org/jira/browse/CASSANDRA-301).
> After adding some more dependencies (ZooKeeper and Lucene deps were missing)
> it installed fine, also removed two other.
> I guess 0.3.0-final could be retrofitted with a POM (the build file for
> Maven). The source does not need to be modified but the retrofitted POM must
> be deployed alongside the generated binary JAR of Cassandra (Maven handles
> this for you, but the repo version of Cassandra will then differ in the
> sense of it having a POM file while the SVN/source version doesn't).

If I understand you correctly, the answer is yes, you would need to
retroactively update 0.3.0. Even for simple changes this is frowned upon
so it sounds like we're talking about a new release (0.3.1) in order to
be able to do this.

> However, some dependencies are defined as system dependencies, meaning that
> the end-user/developer using Cassandra will need provide these dependencies
> themselves.
> This defeats the purpose of the Maven repository system and I guess the only
> reason Hiram put them there was because he couldn't find the needed
> dependencies in publicly available repositories. Perhaps there is a way
> around this? Otherwise, we'll have to find repos that offer these deps
> before we can (safely) put Cassandra in the incubator repo.

Interesting. Could you please update
https://issues.apache.org/jira/browse/CASSANDRA-301 with this
information?

-- 
Eric Evans
eevans@racklabs.com