Error Code Crawler

This maven plugin analyzes invocations of the Exasol error code builder from Java source code. It runs some validations on these definitions, for example, that no error code is defined twice.

Features

Installation

Add the plugin to your pom.xml:

<plugins>
    <plugin>
        <groupId>com.exasol</groupId>
        <artifactId>error-code-crawler-maven-plugin</artifactId>
        <version>LATEST VERSION</version>
        <executions>
            <execution>
                <goals>
                    <goal>verify</goal>
                </goals>
            </execution>
        </executions>
    </plugin>
</plugins>

This will add the plugin to the maven verify lifecycle phase.

Configuration

Each project has an individual error-tag (e.g. EXM). Different sub packages within the project can have different sub tags (EXM-MODEL). This plugin validates that the classes of the project only use the corresponding short tag.

For that you need to configure the project's error-tag mapping in the error_code_config.yml file stored in your project's root directory.

Example:

error-tags:
  EXM:
    packages:
      - com.exasol.example
    highest-index: 3
  EXM-MODEL:
    packages:
      - com.exasol.example.model
    highest-index: 0

This configuration defines which java-packages or classes belong to which error code short tag. A package always includes all sub packages. If two error-tags match, the crawler will take the more specific one.

For example the class com.exasol.example.model.Test belongs to a sub package of com.exasol.example --> ECM and to com.exasol.example.model --> ECM-MODEL. Since the last package name is more specific (longer) this crawler will validate the tag ECM-MODEL for these classes. It will not accept ECM there.

The highest-index property contains the index of the last error code declaration. So in the example the highest error code could be E-EXM-3. This plugin validates that value of this property is higher or equal than the actual highest. You can safely use this property to determine the next error code.

For the moment the value of this property needs to be updated manually.

Excludes

In some very rare cases you may want to exclude some files from crawling. But we don't recommend excluding files.

You can define the excludes by adding the following configuration to the maven-plugin:

<configuration>
    <excludes>
        <exclude>**/MyTest.java</exclude>
    </excludes>
</configuration>

The excludes only affect the validation — not compiling. So if the specific file has syntax errors, excluding won't help.

Keep in mind that error codes from excluded files will not show up in the error catalog and are not validated. So use this option with care!

Source Path

ECM allows you to override the source directories that it crawls.

A common use case for this is when you use project Lombok in your project. In that case crawling the regular sources will fail since the ECM can't find some sources. To fix this you can use the lombok-maven-plugin. This plugin applies the Lombok annotations and generates new source code. To tell ECM to crawl these sources instead use:

<configuration>
    <sourcePaths>
        <sourcePath>target/generated-sources/delombok</sourcePath>
        <sourcePath>target/generated-test-sources/delombok</sourcePath>
    </sourcePaths>
</configuration>

For a working example project with Lombok and error-code-crawler take a look at the virtual-schema-common-document.

If you specify a source path, the plugin assumes that it's generated sources, and for that reason will not add the source location (file + line number) to the report.

Usage

You can also invoke this plugin manually using mvn error-code-crawler:verify.

You can skip the execution of this plugin by either

• adding -Derror-code-crawler.skip=true to your Maven command
• setting the property in your pom.xml (recommended):

  <error-code-crawler.skip>true</error-code-crawler.skip>

• specifying the following configuration in pom.xml:

  <configuration>
      <skip>true</skip>
  </configuration>

Additional Information

• Changelog
• License
• Dependencies
• Features and Requirements
• Design