Repository: logging-log4j2 Updated Branches: refs/heads/master 798e14d4d -> 9662274e2
CLIRR check must be run after install. Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/9662274e Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/9662274e Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/9662274e Branch: refs/heads/master Commit: 9662274e2ad2b8805f0a98ca084ba98e88eb2bc0 Parents: 798e14d Author: Gary Gregory <[email protected]> Authored: Mon Sep 18 08:57:37 2017 -0600 Committer: Gary Gregory <[email protected]> Committed: Mon Sep 18 08:57:37 2017 -0600 ---------------------------------------------------------------------- BUILDING.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/9662274e/BUILDING.md ---------------------------------------------------------------------- diff --git a/BUILDING.md b/BUILDING.md index 9ad551e..d973458 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -35,10 +35,6 @@ To perform the license release audit, a.k.a. "RAT check", run. mvn apache-rat:check -To perform a Clirr check on the API module, run - - mvn clirr:check -pl log4j-api - To build the site with Java 7, make sure you give Maven enough memory using `MAVEN_OPTS` with options appropriate for your JVM. Alternatively, you can build with Java 8 and not deal with `MAVEN_OPTS`. @@ -47,7 +43,9 @@ To install the jars in your local Maven repository, from a command line, run: mvn clean install -Once install is run, you can run the Clirr check on the 1.2 API module: +Once install is run, you can run the Clirr check on the API and 1.2 API modules: + + mvn clirr:check -pl log4j-api mvn clirr:check -pl log4j-1.2-api
