From e3c8f8ef979b4ef0a124060fa3fb0f8e3aa12813 Mon Sep 17 00:00:00 2001
From: dixyushi <72491437+dixyushi@users.noreply.github.com>
Date: Thu, 22 Jul 2021 10:36:03 +0530
Subject: [PATCH 1/4] CobiGen templates configuration-Link fix

---
 documentation/cobigen-maven_configuration.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/cobigen-maven_configuration.asciidoc b/documentation/cobigen-maven_configuration.asciidoc
index 1a0361608a..6fc832cf91 100644
--- a/documentation/cobigen-maven_configuration.asciidoc
+++ b/documentation/cobigen-maven_configuration.asciidoc
@@ -81,7 +81,7 @@ We currently provide a generic deployed version of the templates on the devonfw-
 
 Using the following configuration you will be able to customize your generation as follows:
 
-* `<destinationRoot>` specifies the root directory the relative `destinationPath` of link:cobigen-core_configuration#Templates-configuration[CobiGen templates configuration] should depend on. _Default ${basedir}_
+* `<destinationRoot>` specifies the root directory the relative `destinationPath` of link:cobigen-core_configuration.asciidoc#Templates-configuration[CobiGen templates configuration] should depend on. _Default ${basedir}_
 * `<inputPackage>` declares a package name to be used as input for batch generation. This refers directly to the CobiGen Java Plug-in link:cobigen-javaplugin#ContainerMatcher-types[container matchers of type package] configuration.
 * `<inputFile>` declares a file to be used as input. The CobiGen maven plug-in will try to parse this file to get an appropriate input to be interpreted by any CobiGen plug-in.
 * `<increment>` specifies an link:cobigen-core_configuration#increment-node[increment] ID to be generated. You can specify one single increment with content `ALL` to generate all increments matching the input(s).

From 9400ea67dfe45d40f0f32d4fa31cde72c6f49201 Mon Sep 17 00:00:00 2001
From: dixyushi <72491437+dixyushi@users.noreply.github.com>
Date: Thu, 22 Jul 2021 10:41:32 +0530
Subject: [PATCH 2/4] Update cobigen-maven_configuration.asciidoc

---
 documentation/cobigen-maven_configuration.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/cobigen-maven_configuration.asciidoc b/documentation/cobigen-maven_configuration.asciidoc
index 6fc832cf91..a2ec445983 100644
--- a/documentation/cobigen-maven_configuration.asciidoc
+++ b/documentation/cobigen-maven_configuration.asciidoc
@@ -82,7 +82,7 @@ We currently provide a generic deployed version of the templates on the devonfw-
 Using the following configuration you will be able to customize your generation as follows:
 
 * `<destinationRoot>` specifies the root directory the relative `destinationPath` of link:cobigen-core_configuration.asciidoc#Templates-configuration[CobiGen templates configuration] should depend on. _Default ${basedir}_
-* `<inputPackage>` declares a package name to be used as input for batch generation. This refers directly to the CobiGen Java Plug-in link:cobigen-javaplugin#ContainerMatcher-types[container matchers of type package] configuration.
+* `<inputPackage>` declares a package name to be used as input for batch generation. This refers directly to the CobiGen Java Plug-in link:cobigen-javaplugin.asciidoc#ContainerMatcher-types[container matchers of type package] configuration.
 * `<inputFile>` declares a file to be used as input. The CobiGen maven plug-in will try to parse this file to get an appropriate input to be interpreted by any CobiGen plug-in.
 * `<increment>` specifies an link:cobigen-core_configuration#increment-node[increment] ID to be generated. You can specify one single increment with content `ALL` to generate all increments matching the input(s).
 * `<template>` specifies a link:cobigen-core_configuration#increment-node[template] ID to be generated. You can specify one single template with content `ALL` to generate all templates matching the input(s).

From bba194344e0a42b80da294446d62df652ad27c9c Mon Sep 17 00:00:00 2001
From: dixyushi <72491437+dixyushi@users.noreply.github.com>
Date: Thu, 22 Jul 2021 10:44:24 +0530
Subject: [PATCH 3/4] fixed increment and template link

---
 documentation/cobigen-maven_configuration.asciidoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/documentation/cobigen-maven_configuration.asciidoc b/documentation/cobigen-maven_configuration.asciidoc
index a2ec445983..d39e2da7a2 100644
--- a/documentation/cobigen-maven_configuration.asciidoc
+++ b/documentation/cobigen-maven_configuration.asciidoc
@@ -84,8 +84,8 @@ Using the following configuration you will be able to customize your generation
 * `<destinationRoot>` specifies the root directory the relative `destinationPath` of link:cobigen-core_configuration.asciidoc#Templates-configuration[CobiGen templates configuration] should depend on. _Default ${basedir}_
 * `<inputPackage>` declares a package name to be used as input for batch generation. This refers directly to the CobiGen Java Plug-in link:cobigen-javaplugin.asciidoc#ContainerMatcher-types[container matchers of type package] configuration.
 * `<inputFile>` declares a file to be used as input. The CobiGen maven plug-in will try to parse this file to get an appropriate input to be interpreted by any CobiGen plug-in.
-* `<increment>` specifies an link:cobigen-core_configuration#increment-node[increment] ID to be generated. You can specify one single increment with content `ALL` to generate all increments matching the input(s).
-* `<template>` specifies a link:cobigen-core_configuration#increment-node[template] ID to be generated. You can specify one single template with content `ALL` to generate all templates matching the input(s).
+* `<increment>` specifies an link:cobigen-core_configuration.asciidoc#increment-node[increment] ID to be generated. You can specify one single increment with content `ALL` to generate all increments matching the input(s).
+* `<template>` specifies a link:cobigen-core_configuration.asciidoc#increment-node[template] ID to be generated. You can specify one single template with content `ALL` to generate all templates matching the input(s).
 * `<forceOverride>` specifies an overriding behavior, which enables non-mergeable resources to be completely rewritten by generated contents. For mergeable resources this flag indicates, that conflicting fragments during merge will be replaced by generated content. _Default: false_ 
 * `<failOnNothingGenerated>` specifies whether the build should fail if the execution does not generate anything.
 

From d1a347d6af265b1cabb66f028019f7f6b47d3cac Mon Sep 17 00:00:00 2001
From: dixyushi <72491437+dixyushi@users.noreply.github.com>
Date: Thu, 22 Jul 2021 10:46:11 +0530
Subject: [PATCH 4/4] fixed plug-in mechanism link

---
 documentation/cobigen-maven_configuration.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/cobigen-maven_configuration.asciidoc b/documentation/cobigen-maven_configuration.asciidoc
index d39e2da7a2..7cdcf470e6 100644
--- a/documentation/cobigen-maven_configuration.asciidoc
+++ b/documentation/cobigen-maven_configuration.asciidoc
@@ -119,7 +119,7 @@ Using the following configuration you will be able to customize your generation
 
 == Plugin Injection Since v3
 
-Since version 3.0.0, the link:cobigen-core_configuration#plugin-mechanism[plug-in mechanism] has changed to support modular releases of the CobiGen plug-ins. Therefore, you need to add all plug-ins to be used for generation. Take the following example to get the idea:
+Since version 3.0.0, the link:cobigen-core_configuration.asciidoc#plugin-mechanism[plug-in mechanism] has changed to support modular releases of the CobiGen plug-ins. Therefore, you need to add all plug-ins to be used for generation. Take the following example to get the idea:
 
 .Example of a full configuration including plugins
 ```xml