+0 The bin distribution has a proper notice and license and seems to be properly signed. I still have no idea why it contains the source since that is present in the source jar, speaking of which it is also properly signed and contains the proper notice and license.
I cannot verify the maven artifacts since they have not been published to the staging repository. For example, I'm not sure if the Flume build generates the sources jar for each sub-project, which is what IDE's would like to have along with the "normal" jar. Ralph On Jul 11, 2012, at 4:57 AM, Mike Percy wrote: > This is the first release for Apache Flume as a top-level project, > version 1.2.0. We are voting on release candidate rc1. > > *** Please cast your vote within the next 72 hours *** > > The list of fixed issues: > https://svn.apache.org/repos/asf/flume/tags/flume-1.2.0-rc1/CHANGELOG > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1) > for the source and binary artifacts can be found at: > https://people.apache.org/~mpercy/flume/apache-flume-1.2.0-rc1/ > > The tag to be voted on: > https://svn.apache.org/repos/asf/flume/tags/flume-1.2.0-rc1 > > The KEYS file can be found here: > https://svn.apache.org/repos/asf/flume/dist/KEYS > > Changes since rc0: > - Updated LICENSE file > - Updated DEVNOTES file > - Removed DISCLAIMER file from dist.xml and src.xml manifests > - pom.xml file updated with TLP info (FLUME-1359) > - A build fix to prevent multiple servlet-api jars in lib dir
