HADOOP-17506. Fix typo in BUILDING.txt (#2662)

This commit is contained in:
Gautham B A 2021-01-31 19:48:24 +05:30 committed by GitHub
parent 06e836cd57
commit 9801b78edf
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -103,7 +103,7 @@ Maven main modules:
- hadoop-project (Parent POM for all Hadoop Maven modules. ) - hadoop-project (Parent POM for all Hadoop Maven modules. )
(All plugins & dependencies versions are defined here.) (All plugins & dependencies versions are defined here.)
- hadoop-project-dist (Parent POM for modules that generate distributions.) - hadoop-project-dist (Parent POM for modules that generate distributions.)
- hadoop-annotations (Generates the Hadoop doclet used to generated the Javadocs) - hadoop-annotations (Generates the Hadoop doclet used to generate the Javadocs)
- hadoop-assemblies (Maven assemblies used by the different modules) - hadoop-assemblies (Maven assemblies used by the different modules)
- hadoop-maven-plugins (Maven plugins used in project) - hadoop-maven-plugins (Maven plugins used in project)
- hadoop-build-tools (Build tools like checkstyle, etc.) - hadoop-build-tools (Build tools like checkstyle, etc.)
@ -120,7 +120,7 @@ Maven main modules:
---------------------------------------------------------------------------------- ----------------------------------------------------------------------------------
Where to run Maven from? Where to run Maven from?
It can be run from any module. The only catch is that if not run from utrunk It can be run from any module. The only catch is that if not run from trunk
all modules that are not part of the build run must be installed in the local all modules that are not part of the build run must be installed in the local
Maven cache or available in a Maven repository. Maven cache or available in a Maven repository.
@ -176,7 +176,6 @@ Maven build goals:
we silently build a version of libhadoop.so that cannot make use of snappy. we silently build a version of libhadoop.so that cannot make use of snappy.
This option is recommended if you plan on making use of snappy and want This option is recommended if you plan on making use of snappy and want
to get more repeatable builds. to get more repeatable builds.
* Use -Dsnappy.prefix to specify a nonstandard location for the libsnappy * Use -Dsnappy.prefix to specify a nonstandard location for the libsnappy
header files and library files. You do not need this option if you have header files and library files. You do not need this option if you have
installed snappy using a package manager. installed snappy using a package manager.