update the docs (website guide) to reference the automation for licensing
Project: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/commit/4a24ec23 Tree: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/tree/4a24ec23 Diff: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/diff/4a24ec23 Branch: refs/heads/master Commit: 4a24ec23d187b595f792a7bb8dd90db09d297dfa Parents: 0c9ac7b Author: Alex Heneveld <[email protected]> Authored: Mon Aug 17 15:59:37 2015 +0100 Committer: Alex Heneveld <[email protected]> Committed: Mon Aug 17 17:39:16 2015 +0100 ---------------------------------------------------------------------- docs/guide/dev/code/licensing.md | 6 ++++++ 1 file changed, 6 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/blob/4a24ec23/docs/guide/dev/code/licensing.md ---------------------------------------------------------------------- diff --git a/docs/guide/dev/code/licensing.md b/docs/guide/dev/code/licensing.md index e2a7ef5..8f031e0 100644 --- a/docs/guide/dev/code/licensing.md +++ b/docs/guide/dev/code/licensing.md @@ -78,6 +78,11 @@ When the Brooklyn project makes a release, we produce and release the following Therefore, our source release, our binary release, and every one of our Maven release artifacts, must **each** have their own, individually-tailored, `LICENSE` and `NOTICE` files. +To some extent, this is automated, using scripts in `usage/dist/licensing`; +but this must be manually run, and wherever source code is included or a project has insufficient information in its POM, +you'll need to add project-specific metadata (with a project-specific `source-inclusions.yaml` file and/or in the +dist project's `overrides.yaml` file). See the README.md in that project's folder for more information. + ### Maven artifacts Each Maven module will generally produce a JAR file from code under `src/main`, and a JAR file from code under @@ -114,3 +119,4 @@ each of which have their own license, and which will therefore impact on `LICENS Therefore you must inspect every file that is present in the binary distribution, ascertain its license status, and ensure that `LICENSE` and `NOTICE` are correct. +
