Update docs to be correctly nested and fix attribute issues

Author: jdaugherty

docs/build.gradle

@@ -38,6 +38,8 @@ dependencies {
 }
 
 asciidoctor {
+    inputs.dir layout.projectDirectory.dir('src/docs/asciidoc')
+    outputs.dir layout.buildDirectory.dir('docs/manual')
     baseDirFollowsSourceDir()
     resources {
         from("${project.projectDir}/src/docs/asciidoc/images")
@@ -54,6 +56,9 @@ asciidoctor {
                 'groupId'       : project.group,
                 'artifactId'    : project.name,
                 'sourcedir'     : "${project.projectDir}/src/main/groovy",
+                'migrationPluginExamplesDir' : rootProject.layout.projectDirectory.dir('grails-database-migration/src/integration-test/resources').asFile.absolutePath,
+                'migrationPluginGroupId' : rootProject.findProject(':database-migration').group,
+                'migrationPluginArtifactId' : rootProject.findProject(':database-migration').name,
                 'liquibaseHibernate5Version': liquibaseHibernate5Version
 }
 

docs/src/docs/asciidoc/databaseMigration/configuration.adoc

@@ -1,7 +1,4 @@
-:includedir: _includes
-:integrationtestresources: ../../integration-test/resources
-
-== Configuration
+=== Configuration
 
 There are a few configuration options for the plugin. All configurations are prefixed with `grails.plugin.databasemigration`:
 
@@ -35,7 +32,7 @@ NOTE: All the above configs can be used for multiple datasources
 If secondary dataSource named "second" is configured in application.yml
 [source,yaml]
 ----
-include::{integrationtestresources}/application-multiple-datasource.yml[lines=11..29]
+include::{migrationPluginExamplesDir}/application-multiple-datasource.yml[lines=11..29]
 ----
 
 The configuration for this data source would be:

docs/src/docs/asciidoc/databaseMigration/dbdoc.adoc

@@ -1,4 +1,4 @@
-== DbDoc Controller
+=== DbDoc Controller
 
 You can use the <<ref-documentation-scripts-dbm-db-doc,dbm-db-doc>> script to generate static HTML files to view changelog information, but another option is to use the `DbDocController` at runtime. By default this controller is mapped to `/appname/dbdoc/` but this can be customized with `UrlMappings` like any controller.
 

docs/src/docs/asciidoc/databaseMigration/generalUsage.adoc

@@ -1,4 +1,4 @@
-== General Usage
+=== General Usage
 
 After creating the initial changelog, the typical workflow will be along the lines of:
 
@@ -9,10 +9,10 @@ After creating the initial changelog, the typical workflow will be along the lin
 * check the updated domain class(es) and changelog(s) into source control
 
 [WARNING]
-====
+=====
 1. When running migration scripts on non-development databases, it's important that you backup the database before running the migration in case anything goes wrong. You could also make a copy of the database and run the script against that, and if there's a problem the real database will be unaffected.
 2. Setting the dbCreate setting to "none" is recommended when executing the dbm migration commands. Otherwise you might run into troubles and the commands could not be executed.
-====
+=====
 
 To create the changelog additions, you can either manually create the changes or with the <<ref-diff-scripts-dbm-gorm-diff,dbm-gorm-diff>> script (you can also use the <<ref-diff-scripts-dbm-diff,dbm-diff>> script but it's far less convenient and requires a 2nd temporary database).
 
@@ -24,7 +24,7 @@ You have a few options with `dbm-gorm-diff`:
 Regardless of which approach you use, be sure to inspect generated changes and adjust as necessary.
 
 
-=== Autorun on start
+==== Autorun on start
 
 
 Since Liquibase maintains a record of changes that have been applied, you can avoid manually updating the database by taking advantage of the plugin's auto-run feature. By default this is disabled, but you can enable it by adding

docs/src/docs/asciidoc/databaseMigration/gettingStarted.adoc

@@ -1,4 +1,4 @@
-== Getting Started
+=== Getting Started
 
 *The first step is to add a dependency for the plugin in `build.gradle`:*
 
@@ -7,13 +7,13 @@
 buildscript {
    dependencies {
       ...
-      classpath '{groupId}:{artifactId}:{version}'
+      classpath '{migrationPluginGroupId}:{migrationPluginArtifactId}:{version}'
    }
 }
 
 dependencies {
    ...
-     implementation '{groupId}:{artifactId}:{version}'
+     implementation '{migrationPluginGroupId}:{migrationPluginArtifactId}:{version}'
 }
 ----
 

docs/src/docs/asciidoc/databaseMigration/gorm.adoc

@@ -1,4 +1,4 @@
-== GORM Support
+=== GORM Support
 
 The plugin's support for GORM is one feature that differentiates it from using Liquibase directly. Typically, when using Liquibase you make changes to a database yourself, and then create changesets manually, or use a diff script to compare your updated database to one that hasn't been updated yet. This is a decent amount of work and is rather error-prone. It's easy to forget some changes that aren't required but help performance, for example creating an index on a foreign key when using MySQL.
 

docs/src/docs/asciidoc/databaseMigration/groovyChanges.adoc

@@ -1,10 +1,10 @@
-== Groovy Changes
+=== Groovy Changes
 
 In addition to the built-in Liquibase changes (see http://www.liquibase.org/manual/home[the documentation] for what's available) you can also make database changes using Groovy code (as long as you're using the Groovy DSL file format). These changes use the `grailsChange` tag name and are contained in a `changeSet` tag like standard built-in tags.
 
 There are four supported inner tags and two callable methods (to override the default confirmation message and checksum value).
 
-=== General format
+==== General format
 
 This is the general format of a Groovy-based change; all inner tags and methods are optional:
 
@@ -50,7 +50,7 @@ databaseChangeLog = {
 }
 ----
 
-=== Available variables
+==== Available variables
 
 These variables are available throughout the change closure:
 

docs/src/docs/asciidoc/databaseMigration/groovyPreconditions.adoc

@@ -1,8 +1,8 @@
-== Groovy Preconditions
+=== Groovy Preconditions
 
 In addition to the built-in Liquibase preconditions (see http://www.liquibase.org/manual/preconditions[the documentation] for what's available) you can also specify preconditions using Groovy code (as long as you're using the Groovy DSL file format). These changes use the `grailsPrecondition` tag name and are contained in the `databaseChangeLog` tag or in a `changeSet` tag like standard built-in tags.
 
-=== General format
+==== General format
 
 This is the general format of a Groovy-based precondition:
 
@@ -49,7 +49,7 @@ As you can see there are a few ways to indicate that a precondition wasn't met:
 * call the `fail(String message)` method (throws a `PreconditionFailedException`)
 * throw an exception (shouldn't be necessary - use `assert` or `fail()` instead)
 
-=== Available variables
+==== Available variables
 
 * `database` - the current Liquibase `Database` instance
 * `databaseConnection` - the current Liquibase `DatabaseConnection` instance, which is a wrapper around the JDBC `Connection` (but doesn't implement the `Connection` interface)
@@ -61,7 +61,7 @@ As you can see there are a few ways to indicate that a precondition wasn't met:
 * `changeSet` - the current Liquibase `ChangeSet` instance
 * `changeLog` - the current Liquibase `DatabaseChangeLog` instance
 
-=== Utility methods
+==== Utility methods
 
 * `createDatabaseSnapshotGenerator()` - retrieves the `DatabaseSnapshotGenerator` for the current `Database`
 * `createDatabaseSnapshot(String schemaName = null)` - creates a `DatabaseSnapshot` for the current `Database` (and schema if specified)

docs/src/docs/asciidoc/databaseMigration/index.adoc

@@ -1,9 +1,3 @@
-:includedir: _includes
-
-= Grails Database Migration Plugin
-:source-highlighter: coderay
-:numbered:
-
 [[introduction]]
 include::introduction.adoc[]
 
@@ -29,10 +23,10 @@ include::gorm.adoc[]
 include::dbdoc.adoc[]
 
 [[reference]]
-== Reference
+=== Reference
 
 [[ref-diff-scripts]]
-=== Diff Scripts
+==== Diff Scripts
 
 [[ref-diff-scripts-dbm-diff]]
 include::ref/Diff Scripts/dbm-diff.adoc[]
@@ -41,13 +35,13 @@ include::ref/Diff Scripts/dbm-diff.adoc[]
 include::ref/Diff Scripts/dbm-gorm-diff.adoc[]
 
 [[ref-documentation-scripts]]
-=== Documentation Scripts
+==== Documentation Scripts
 
 [[ref-documentation-scripts-dbm-db-doc]]
 include::ref/Documentation Scripts/dbm-db-doc.adoc[]
 
 [[ref-maintenance-scripts]]
-=== Maintenance Scripts
+==== Maintenance Scripts
 
 [[ref-maintenance-scripts-dbm-add-migration]]
 include::ref/Maintenance Scripts/dbm-add-migration.adoc[]
@@ -125,7 +119,7 @@ include::ref/Rollback Scripts/dbm-rollback-to-date.adoc[]
 include::ref/Rollback Scripts/dbm-rollback.adoc[]
 
 [[ref-update-scripts]]
-=== Update Scripts
+==== Update Scripts
 
 [[ref-update-scripts-dbm-previous-changeset-sql]]
 include::ref/Update Scripts/dbm-previous-changeset-sql.adoc[]

docs/src/docs/asciidoc/databaseMigration/introduction.adoc

@@ -1,4 +1,4 @@
-== Introduction to the Database Migration Plugin
+=== Introduction
 
 The Database Migration plugin helps you manage database changes while developing Grails applications. The plugin uses the http://www.liquibase.org/[Liquibase] library.