manage.bat(sh) => 23 (generate):
A execution command of Generate task
which generates classes corresponding your tables,
for example, entities, condition-beans to specified
directories by DBFlute properties on "dfprop" directory.

Generated structures (directories and classes) are like this:
/- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
allcommon : classes bridging to DBFlute Runtime
bsbhv     : base behaviors
bsentity  : base entities

        return classes.values().findAll { !it.name.contains('.internal.') }
    }

    boolean isKnownType(String className) {
        return classMetaData.find(className) != null
    }

    gradlebuild.docs.dsl.docbook.model.ClassDoc findClassDoc(String className) {
        gradlebuild.docs.dsl.docbook.model.ClassDoc classDoc = classes[className]

  }

  public void testFindClassesToTest_withCorrespondingTestClassAndExplicitlyTested() {
    ImmutableList<Class<?>> classes = ImmutableList.of(Foo.class, FooTest.class);
    assertThat(findClassesToTest(classes, "testPublic")).isEmpty();
    assertThat(findClassesToTest(classes, "testNotThere", "testPublic")).isEmpty();
  }

  public void testFindClassesToTest_withCorrespondingTestClass_noTestName() {

import org.apache.maven.api.di.Named;

/**
 * Annotation processor that generates an index file for classes annotated with {@link Named}.
 * This processor scans for classes with the {@code @Named} annotation and creates a file
 * at {@code META-INF/maven/org.apache.maven.api.di.Inject} containing the fully qualified
 * names of these classes.
 *
 * @since 4.0.0
 */
@SupportedAnnotationTypes("org.apache.maven.api.di.Named")

mvn verify                            # Generate coverage report
```

## Code Conventions

### Class Structure

- **Utility classes**: `abstract` class + `protected` constructor
- **Constants classes**: Same pattern

### Argument Validation

Use `AssertionUtil` at method entry:
- `AssertionUtil.assertArgumentNotNull("argName", value)`

      if (lastDollarSign != -1) {
        String innerClassName = className.substring(lastDollarSign + 1);
        // local and anonymous classes are prefixed with number (1,2,3...), anonymous classes are
        // entirely numeric whereas local classes have the user supplied name as a suffix
        return CharMatcher.inRange('0', '9').trimLeadingFrom(innerClassName);
      }
      String packageName = getPackageName();

     *       <td>{@code target/classes}</td>
     *       <td>Compiled application classes and processed main resources</td>
     *     </tr>
     *     <tr>
     *       <td>{@link ProjectScope#TEST}</td>
     *       <td>{@code build.getTestOutputDirectory()}</td>
     *       <td>{@code target/test-classes}</td>
     *       <td>Compiled test classes and processed test resources</td>
     *     </tr>

 *   <li>{@link Stopwatch}
 *   <li>{@link Throwables}
 *   <li>{@link Verify}
 * </ul>
 *
 * <h3>The rest</h3>
 *
 * This package also contains some classes with niche use cases (e.g., {@link Utf8} and {@link
 * Defaults}), as well as a number of classes that have been superseded by additions to the JDK.
 */
@CheckReturnValue
@NullMarked
package com.google.common.base;

			<outputDirectory>fess-${project.version}/lib/classes</outputDirectory>
		</fileSet>
		<fileSet>
			<directory>${project.build.directory}/fess/WEB-INF/classes/org/codelibs/fess/</directory>
			<includes>
				<include>FessBoot**</include>
				<include>tomcat/**</include>
			</includes>
			<outputDirectory>fess-${project.version}/lib/classes/org/codelibs/fess</outputDirectory>
		</fileSet>
		<fileSet>

### Properties in entirely new classes

When developing an entirely new class (task, extension, domain object, etc), the API should consist of managed lazy properties.

Preferably, these new classes should be 100% managed and have their implementation generated by Gradle at runtime.