You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by gg...@apache.org on 2016/05/26 18:22:11 UTC
logging-log4j2 git commit: Update build instructions: the 1.2 API
Clirr check MUST come AFTER install is run. This is not obvious when you run
from a SNAPSHOT build,
but it must be so for a version that you have never built before.
Repository: logging-log4j2
Updated Branches:
refs/heads/master 219013bc4 -> 434528a96
Update build instructions: the 1.2 API Clirr check MUST come AFTER
install is run. This is not obvious when you run from a SNAPSHOT build,
but it must be so for a version that you have never built before.
Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/434528a9
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/434528a9
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/434528a9
Branch: refs/heads/master
Commit: 434528a968c024e1086b98ad4cf3d4598d5f36f0
Parents: 219013b
Author: ggregory <gg...@apache.org>
Authored: Thu May 26 11:22:06 2016 -0700
Committer: ggregory <gg...@apache.org>
Committed: Thu May 26 11:22:06 2016 -0700
----------------------------------------------------------------------
BUILDING.txt | 96 +++++++++++++++++++++++++++++--------------------------
1 file changed, 51 insertions(+), 45 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/434528a9/BUILDING.txt
----------------------------------------------------------------------
diff --git a/BUILDING.txt b/BUILDING.txt
index 84dbc0e..33bfdcb 100644
--- a/BUILDING.txt
+++ b/BUILDING.txt
@@ -1,45 +1,51 @@
-Building Log4j 2
-
-To build Log4j 2, you need a JDK implementation version 1.7 or greater, and Apache Maven.
-Note that building the site requires Maven 3.0.5, while everything else works
-fine with any version of Maven 3.
-
-To perform the license release audit, a.k.a. "RAT check", run.
-
-mvn apache-rat:check
-
-To perform a Clirr check on the API modules, run
-
-mvn clirr:check -pl log4j-api
-mvn clirr:check -pl log4j-1.2-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.
-
-To build the site, from a command line, run:
-
-mvn clean install
-mvn site
-
-On Windows, use a local staging directory, for example:
-
-mvn site:stage-deploy -DstagingSiteURL=file:///%HOME%/log4j
-
-On UNIX, use a local staging directory, for example:
-
-mvn site:stage-deploy -DstagingSiteURL=file:///$HOME/log4j
-
-To test, run:
-
-mvn test
-
-Then, to test OSGi, you must first create the jars:
-
-mvn install -DskipTests
-mvn package -DskipTests
-
-Next, you can run the tests as usual, which will pick up the jar files to use as OSGi bundles from the various target
-directories:
-
-mvn test
+Building Log4j 2
+
+To build Log4j 2, you need a JDK implementation version 1.7 or greater, and Apache Maven.
+Note that building the site requires Maven 3.0.5, while everything else works
+fine with any version of Maven 3.
+
+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.
+
+To build the site, from a command line, run:
+
+mvn clean install
+
+Once install is run, you can run the Clirr check on the 1.2 API module:
+
+mvn clirr:check -pl log4j-1.2-api
+
+Next, to build the site:
+
+mvn site
+
+On Windows, use a local staging directory, for example:
+
+mvn site:stage-deploy -DstagingSiteURL=file:///%HOME%/log4j
+
+On UNIX, use a local staging directory, for example:
+
+mvn site:stage-deploy -DstagingSiteURL=file:///$HOME/log4j
+
+To test, run:
+
+mvn test
+
+Then, to test OSGi, you must first create the jars:
+
+mvn install -DskipTests
+mvn package -DskipTests
+
+Next, you can run the tests as usual, which will pick up the jar files to use as OSGi bundles from the various target
+directories:
+
+mvn test