Hi, > This is a known problem. Please help out.
That is the reason of having those jars in the source release? Could it just be replaced by a series of curl commands in a shell script? I can help fix up the LICENSE and NOTICE files, but the inclusion of compiled code in a source release is the bigger is here. > It has been made mention of on most of the recent vote release threads, and > we have a ticket CASSANDRA-16391 open to deal with it (eta is immediately > after 4.0). I'm not sure that fixing this after a 4.0 release would be an option and the question may come up of what needs to be done with the source releases that are already public. Including Category B binaries in a source release is mentioned in ASF policy here [1]. Thanks, Justin 1. https://apache.org/legal/resolved.html#binary-only-inclusion-condition --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
