diff options
| author |   liamfallon <liam.fallon@est.tech> | 2020-10-16 13:09:11 +0100 |
|---|---|---|
| committer | liamfallon <liam.fallon@est.tech> | 2020-10-16 13:09:16 +0100 |
| commit | 0cf967c0239a8ab9c8b8831b700b72d9a08f7b03 (patch) | |
| tree | a4fbcd97008769d55ac443bc22abf517308bf6a7 /src/site-docs/adoc/fragments/howto-codestyle/30-configure-checkstyle-maven.adoc | |
| parent | 9833876720ff14517ee78bda557e6021df723800 (diff) | |
Remove apex asciidoc documents
Apex documentation has now all been ported to use the ONAP recommended
rst format. This review removes the old asciidoc documents.
Issue-ID: POLICY-2824
Change-Id: I562bd344cb7d6ff36e7d54bdb8f95e3b656468f8
Signed-off-by: liamfallon <liam.fallon@est.tech>
Diffstat (limited to 'src/site-docs/adoc/fragments/howto-codestyle/30-configure-checkstyle-maven.adoc')
| -rw-r--r-- | src/site-docs/adoc/fragments/howto-codestyle/30-configure-checkstyle-maven.adoc | 24 |
1 files changed, 0 insertions, 24 deletions
diff --git a/src/site-docs/adoc/fragments/howto-codestyle/30-configure-checkstyle-maven.adoc b/src/site-docs/adoc/fragments/howto-codestyle/30-configure-checkstyle-maven.adoc deleted file mode 100644 index d59b424af..000000000 --- a/src/site-docs/adoc/fragments/howto-codestyle/30-configure-checkstyle-maven.adoc +++ /dev/null @@ -1,24 +0,0 @@ -// -// ============LICENSE_START======================================================= -// Copyright (C) 2016-2018 Ericsson. All rights reserved. -// ================================================================================ -// This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE -// Full license text at https://creativecommons.org/licenses/by/4.0/legalcode -// -// SPDX-License-Identifier: CC-BY-4.0 -// ============LICENSE_END========================================================= -// -// @author Sven van der Meer (sven.van.der.meer@ericsson.com) -// - -== Configure Checkstyle (Maven) - -When using a custom style configuration with Checkstyle, the definition of that style must of course be available to Checkstyle. -In order not to have to distribute style files for checkstyle into all Maven modules, it is recommended that a special Maven module be built that contains the checkstyle style definition. -That module is then used as a dependency in the __POM__ for all other modules that wish to use that checkstyle style. -For a full explanation see link:https://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html[the explanation of Checkstyle multi-module configuration]. - -For APEX, the ONAP checkstyle rules do apply. -The configuration is part of the ONAP parent. -See link:https://git.onap.org/oparent/plain/checkstyle/src/main/resources/onap-checkstyle/[ONAP Git] for details and updates. - |