JarCasting
config-doclet
Javadoc Doclet that produces a configuration help file for your project. This uses the JDK 9 Doclet API, with all the fun that entails.
If you're like me, your programs often have code like this:
private static final String CFG_FOO = "app.stuff.foo";
private static final String DEFAULT_FOO = "bar";
// ...
Properties config = getAppConfig();
System.out.println("The foo is " + config.getProperty(CFG_FOO, DEFAULT_FOO));
That is, a program reads configuration parameters from text files, and the strings used to get the setting values from a Properties object are defined as constants. Frequently, the default values are defined as constants.
When it comes time to tell your users how your program can be configured, you have to manually write up documentation with all the constant values with descriptions and default values. That's a pain because it's a lot of extra work and it becomes obsolete when the code changes.
This doclet allows you to generate user-facing documentation about your configuration settings from Javadoc comments on the static final fields that define your configuration keys. This helps you keep your program's documentation complete and in sync with the source code while not requiring that your users dig into the source code or API docs.
The plugin assumes that you want output suitable for a .properties file. As an alternative, you can generate JSON-formatted output and use your own subsequent plugins or programs to transform that into human-readable documentation.
Overview
Consider this example class:
public class App {
/**
* Setting that specifies the message to print.
* @cfg.default hello
* @cfg.example Goodbye!
*/
public static final String CFG_MESSAGE = "app.message";
private Properties config;
public App(Properties config) {
this.config = config;
}
public void printMessage() {
String message = config.getProperty(CFG_MESSAGE, "hello");
System.out.println(message);
}
}
If we execute the doclet on this source code with the default settings, the generated file will contain the following contents:
# Setting that specifies the message to print.
# Example: Goodbye!
#app.message = hello
The doclet examines each static final field whose name has the prefix CFG_. For each one, the description is taken from the regular comment body plus special block tags. The field selection criterion can be customized with command line options and the description can be fine-tuned with the block tags described below.
Tag Reference
@cfg.defaultspecifies the setting's default value@cfg.exampleprovides an example of an acceptable value for the setting@cfg.descriptionspecifies text to override the regular comment body for the description@cfg.keyspecifies a string that overrides the value of the constant; use this if your constant value is not available at compile-time@cfg.includeforces a setting to be include even when other attributes would cause it to be excluded; for example, deprecated constants are normally excluded, but tagging them with this would retain them@cfg.sortKeyspecifies a string to use instead of the setting key when sorting the settings for printing
Doclet Options
- --field-names restricts the static final fields examined to those whose names match the argument; you can use wildcards
?and*and delimit patterns with commas, e.g.KEY_*,CONFIG_* - --field-names-regex restricts the static final fields examined to those whose names match the argument Java-syntax regex
- --output-filename sets the output filename
- --output-directory sets the output directory
- --output-format sets the output format (one of
propertiesorjson; default isproperties) - --assign-value in properties output, determines whether a value is assigned (and not commented-out); argument must be
auto,always, ornever; never means the assignment is commented out, always means it is not, and auto means the system decides based on the value - -header prepends a string to the output; use a
file:URL to read the string from file - -footer appends a string to the output; use a
file:URL to read the string from file - -docencoding specifies the output charset
Using as a Maven plugin
This is not a Maven plugin, but the maven-javadoc-plugin can be configured to use this doclet.
<build>
<plugins>
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<version>3.0.1</version>
<executions>
<execution>
<id>generate-config-help</id>
<goals>
<goal>javadoc</goal>
</goals>
<phase>generate-resources</phase>
<configuration>
<doclet>io.github.mike10004.configdoclet.ConfigDoclet</doclet>
<docletArtifact>
<groupId>com.github.mike10004</groupId>
<artifactId>config-doclet-core</artifactId>
<version>LATEST</version> <!-- see Maven badge above -->
</docletArtifact>
<reportOutputDirectory>${project.build.directory}/help</reportOutputDirectory>
<additionalOptions>
<arg>'--field-names=MY_CFG_CONST_PREFIX_*'</arg>
</additionalOptions>
<show>private</show>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
This will generate a file named target/help/config-doclet-output.properties in your project directory.
If you are also generating regular API docs, you may need to add some configuration parameters to ignore this doclet's tags (which all have prefix cfg.), or use <doclint>none</doclint> to ignore non-fatal errors during Javadoc generation.
Running from the command line
Running from the command line is a bit burdernsome because the doclet has some dependencies, but it can be done with a command like this:
javadoc -doclet io.github.mike10004.configdoclet.ConfigDoclet \
-docletpath /path/to/config-doclet.jar:/path/to/jsr305-3.0.2.jar:/path/to/commons-lang3-3.6.jar:/path/to/gson-2.8.5.jar \
'--field-names=CFG_*' com.example
Adjust the command arguments to contain the correct values for the locations of your JAR files, the names of your constant fields, and your source packages.