> The binary release artifacts created by the `release' target in > build.xml, (they look something like > apache-cassandra-$VERSION-bin.tar.gz on the mirrors).
actually I was asking about the problematic artifacts inside that distribution that were in question as to whether you could redistribute or not, the licenses mentioned below are enough to go on http://www.apache.org/legal/resolved.html looking through there ought to answer a lot of the questions, but if your in doubt on anything in particular I would recommend assembling a list of all the dependencies you want to redistibute and their associated licenses and compile it all into an issue on the LEGAL jira project. that way you guys are clear on what you can and can't redistribute in official apache releases cheers, jesse >> apache legal has been very helpful on this in the past for maven, and >> the maven release process has done a lot of work in terms of making >> the release process at apache sane and legal > > I've tried to find comparable maven or ivy-based projects to see how > others handle this, (without luck). Comparable here means having release > artifacts that are more than just jars, (i.e. containing config samples, > startup scripts, etc), with dependencies not developed at the ASF, and > which cover a range of different licensing (MIT, BSD, Public domain, > etc). > > Again, having our cake and eating too would be better than choosing the > lesser of evils, so any suggestions would be well received. > > -- > Eric Evans > eev...@rackspace.com > >
