Skip to content

Commit 39c7455

Browse files
authored
HBASE-30056: Fix markdown in hbase-archetypes README.md (#8025)
Signed-off-by: Peter Somogyi <psomogyi@apache.org> Signed-off-by: Xiao Liu <liuxiaocs@apache.org> Reviewed-by: Rahul Agarkar <ragarkar@cloudera.com>
1 parent 0c11338 commit 39c7455

1 file changed

Lines changed: 8 additions & 8 deletions

File tree

hbase-archetypes/README.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,9 @@ specific language governing permissions and limitations
1717
under the License.
1818
-->
1919

20-
#hbase-archetypes
20+
# hbase-archetypes
2121

22-
##Overview
22+
## Overview
2323
The hbase-archetypes subproject of hbase provides an infrastructure for
2424
creation and maintenance of Maven archetypes<sup id="a1">[1](#f1)</sup>
2525
pertinent to HBase. Upon deployment to the archetype
@@ -30,9 +30,9 @@ end-user developers to autogenerate completely configured Maven projects
3030
`archetype:generate` goal of the
3131
maven-archetype-plugin<sup id="a4">[4](#f4)</sup>.
3232

33-
##Notes for contributors and committers to the HBase project
33+
## Notes for contributors and committers to the HBase project
3434

35-
####The structure of hbase-archetypes
35+
#### The structure of hbase-archetypes
3636
The hbase-archetypes project contains a separate subproject for each archetype.
3737
The top level components of such a subproject comprise a complete, standalone
3838
exemplar Maven project containing:
@@ -47,7 +47,7 @@ code `./src/main/.../HelloHBase.java` and `./src/test/.../TestHelloHBase.java`,
4747
(b) a `pom.xml` file establishing dependency upon hbase-client and test-scope
4848
dependency upon hbase-testing-util, and (c) a `log4j.properties` resource file.
4949

50-
####How archetypes are created during the hbase install process
50+
#### How archetypes are created during the hbase install process
5151
During the `mvn install` process, all standalone exemplar projects in the
5252
`hbase-archetypes` subdirectory are first packaged/tested/installed, and then
5353
the following steps are executed in `hbase-archetypes/hbase-archetype-builder`
@@ -74,7 +74,7 @@ repository. (Note that installation of an archetype automatically includes
7474
invocation of integration-testing prior to install, which performs a test
7575
generation of a project from the archetype.)
7676

77-
####How to add a new archetype to the hbase-archetypes collection
77+
#### How to add a new archetype to the hbase-archetypes collection
7878
1. Create a new subdirectory in `hbase-archetypes`, populated with a
7979
completely configured Maven project, which will serve as the exemplar project
8080
of the new archetype. (It may be most straightforward to simply copy the `src`
@@ -93,7 +93,7 @@ elements and `<transformationSet>` elements within the `<plugin>` elements
9393
`createArchetypes.sh` and `installArchetypes.sh` scripts in the
9494
`hbase-archetype-builder` subdirectory (using the existing entries as a guide).
9595

96-
####How to do additional testing/inspection of an archetype in this collection
96+
#### How to do additional testing/inspection of an archetype in this collection
9797
Although integration-testing (which is automatically performed for each
9898
archetype during the install process) already performs test generation of a
9999
project from an archetype, it may often be advisable to do further manual
@@ -106,7 +106,7 @@ and can be tested locally by executing the following:
106106
This displays a numbered list of all locally-installed archetypes for the user
107107
to choose from for generation of a new Maven project.
108108

109-
##Footnotes:
109+
## Footnotes:
110110
<b id="f1">1</b> -- [Maven Archetype
111111
](http://maven.apache.org/archetype/index.html) ("About" page).
112112
-- [](#a1)

0 commit comments

Comments
 (0)