OK, to keep everyone up to date, I have been working on getting the one non-ASL licensed dependency that is not in central into central (high-scale-lib)...
Should have that sorted soon enough, at which point my plan is as follows. Get the 0.7.0 release in central in its current uber-jar form... it would be nice to have this split into the client libraries... but at this point in time that seems to be seen as too much risk for 0.7.0, so I'll not fight that. Any ASL licensed dependencies not already in central will be pushed to central under the org.apache.cassandra groupId (i.e. libthrift, etc) The cassandra project is already redistributing these artifacts, so there is no harm in doing that via central. Then try and help in splitting out the next version into separate jars.... and try and help the upstream ASL licensed projects to get into central (I note that libthrift is supposed to be making progress) This may require me to get my hands really dirty and try and help hadoop get a release out.... ;-) -Stephen On 14 December 2010 23:52, Eric Evans <eev...@rackspace.com> wrote: > On Tue, 2010-12-14 at 19:39 +0000, Stephen Connolly wrote: >> Well one piece of evidence is that the ivy.xml does not look to have >> been kept in sync with the binaries in the lib directory... That is my >> argument for not keeping binaries in lib folders... > > No, the contents of lib/ are runtime dependencies; It's what gets rolled > into release artifacts. Ivy is used to retrieve build dependencies. > > -- > Eric Evans > eev...@rackspace.com > >
