Hi, On Mon, Mar 26, 2012 at 6:05 PM, Roy T. Fielding <field...@gbiv.com> wrote: > Second, Apache projects only release SOURCE. We don't release > third party binaries, period. Hence, the specific examples that > you provided are not valid for a release LICENSE. They might be > valid for the license file included within a binary package, but > please note that such a license file will be different from the > LICENSE that is provided in the source distribution, and is not > something we would be voting upon (because no PMC can be expected > to verify the validity of those binaries).
In this case the binaries need to be included in the source package as they are needed as dependencies for the build to work (the binaries are included in svn as well). This is a common scenario for pretty much all Java projects that don't use a dependency manager like Maven to automatically pull in dependencies at build time. The alternative to including binary jars would be to ship the source code of upstream libraries and include them in the main build, but that's contrary to standard practice for Ant projects and goes against the documented policy for "category B" licenses (http://www.apache.org/legal/resolved.html#category-b). > Hopefully, Jukka can step in and document how the LICENSE and > NOTICE files are crafted for Jackrabbit and Sling, since those > projects have the exact same issues regarding third-party libraries > that are only included in the binary packages. The difference here is that Jackrabbit and Sling are built with Maven so we don't need to ship upstream dependencies along with the source code we wrote here at Apache. BR, Jukka Zitting --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
