A Doclet that allows the use of Markdown and PlantUML in JavaDoc comments. It uses Pegdown as Markdown processor. It's a simple preprocessor to the standard Doclet: It processes all JavaDoc comments in the documentation tree and then forwards the result to the standard Doclet. The JavaDoc output by this Doclet for this Doclet can be found here.
This Doclet is released under the GPL 3.0.
Sometimes, leading whitespaces are significant in Markdown. Because of the way we usually write JavaDoc comments and the way JavaDoc is implemented, this may lead to some problems:
/**
* Title
* =====
*
* Text
*/
In this example, each line has one leading space. Because of this, the title won't be recognised as such by Pegdown. To work around this problem, the Doclet uses a simple trick: The first leading space character (the actual space character, i.e. \\u0020) will be cut off, if it exists.
This may be important e.g. for code blocks, which should be indented by 4 spaces: Well, it's 5 spaces now. ;)
Note: If an overview.md file is specified, leading spaces will be treated normally in this file. The first space will not be ignored.
This behaviour is currently not customisable.
The following known tags handled by Pegdown so you can use Markup with them:
@author@version@return@deprecated@since@param@throws
The @see tag is a special case, as there are several variants of this tag. These two variants will remain unchanged:
- Javadoc-Links:
@see Foo#bar() - Links:
@see <a href="http://www.example.com/">Example</a>
The third variant however, which is originally meant to refer to a printed book, may also contain Markdown-style links:
@see "[Example](http://www.example.com/)"@see "<http://www.example.com/>"@see "Example <http://www.example.com/>"@see "[[http://www.example.com/]]"@see "[[http://www.example.com/ Example]]"
These are all rendered as @see <a href="http://www.example.com/">LABEL</a>, where LABEL falls back to the link's URL, if no label is given.
Tag handling can be customised by implementing your own TagRenderers and registering them with the PegdownDoclet. You'll have to write your own Doclet, though, there's currently no way to do this using the command line. See the JavaDocs and sources for details on this.
This currently only works for block tags.
'@' at the beginning of a new line introduces the tag block. This is very inconvenient especially in example code blocks:
/**
* Java Example:
*
* ```java
* @Override
* public void myMethod() {
* }
* ```
*/The tag block will start with @Override and the rest of the documentation block will be cut off. There's unfortunately no way to circumvent this. However, the Doclet provides a discrete way to escape such leading '@' signs:
/**
* Java Example:
*
* ```java
* .@Override
* public void myMethod() {
* }
* ```
*/Note the leading dot in .@Override. This dot will not be rendered in the JavaDoc. If you really meant .@, add another dot: ..@ will be rendered as .@. This only works for the '@' sign and only at the beginning of a line.
How to define your own Markdown Taglet
see Description Of Gist Taglet
This Doclet has built-in support for PlantUML. Just use the @uml tag:
/**
* Description.
*
* 
*
* @uml example.png
* Alice -> Bob: Authentication Request
* Bob --> Alice: Authentication Response
*/
It's also possible to use @startuml and @enduml instead, as usual. @startuml is simply a synonym for @uml and @enduml will be ignored entirely. Use this for compatibility with other tools, like e.g. the PlantUML IDEA Plugin.
The Pegdown Doclet integrates highlight.js to enable syntax highlighting in code examples. See "Fenced code blocks" below for details.
Download markdown-doclet-<version>-all.jar from the Maven repository and specify it on the command line:
javadoc -doclet ch.raffael.mddoclet.MarkdownDoclet -docletpath /path/to/markdown-doclet-<version>-all.jar
It supports all options the standard Doclet supports and some additional options:
-
-extensions <ext>: Specify the Pegdown extensions. The extensions list a comma separated list of constants as specified in org.pegdown.Extensions, converted to upper case and '-' replaced by '_'. The default isautolinks,definitions,smartypants,tables,wikilinks. -
-overview <page>: Specify an overview page. This is basically the same as with the standard Doclet, however, the specified page will be rendered using Pegdown -
-plantuml-config <file>: A configuration file that will be included before each diagram. -
-highlight-style <style>: The style to be used for syntax highlighting. -
-disable-highlight: Disable syntax highlighting entirely. -
-enable-auto-highlight: Enable auto-highlighting. If no language is specified in code blocks, the highlighter will try to guess the correct language. -
-todo-title: Set the title of TODO boxes. -
-parse-timeout <seconds>: Set the parse timeout for Pegdown. The default is 2 seconds. Try raising the parse timeout if you encounter timeout errors when generating your JavaDocs. You may also specify fractions of seconds (e.g. 2.5). -
-javadocversion <version>: Set the version of JavaDoc that's invoking this Doclet. This is used to adapt to some quirks, currently to use different default CSS files for JDK 7 and 8. The default is the version currently running JVM, which is usually the right thing. If you have to override it, currently supported values arev7orv8.
There's an annoying issue with Javadoc: If the locale is not set to exactly en, it won't work with HTML tags correctly when determining the first sentence. For instance, of you start your comment with a title (which using Markdown actually encourages to do, at least in package descriptions), the closing </h1> tag will not be recognised:
/**
* * My Title
*
* Text goes here. More details follow.
*/With a locale other than 'en', only the dot ('.') is recognised as sentence end resulting in the following summary:
My Title Text goes here.
If the locale is en and no break iterator is set, the </h1> after "My Title" is recognised as sentence end.
I'd therefore recommend to set the locale explicitly to en.
See also: Issue #44
Add the following to your build.gradle to use the doclet with Gradle:
buildscript {
repositories {
mavenCentral() // or jcenter()
}
dependencies {
classpath 'ch.raffael.markdown-doclet:markdown-doclet:1.4'
}
}
apply plugin: 'ch.raffael.markdown-doclet'Add the following to your POM to use the doclet with Maven:
<build>
<plugins>
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.9</version>
<configuration>
<doclet>ch.raffael.mddoclet.MarkdownDoclet</doclet>
<docletArtifact>
<groupId>ch.raffael.markdown-doclet</groupId>
<artifactId>markdown-doclet</artifactId>
<version>1.4</version>
</docletArtifact>
<useStandardDocletOptions>true</useStandardDocletOptions>
</configuration>
</plugin>
</plugins>
</build>The doclet is available in Maven Central.
There is a plugin that enables Ctrl-Q in IntelliJ IDEA. Just download it from the plugin repository ("Settings -- Plugins -- Browse Repositories"), or build it yourself (see integrations/idea-plugin/README.md).
Use the PlantUML integration plugin for a live preview while editing PlantUML diagrams. This only works if you use the "classic" @startuml and @enduml tags.
If you think your favourite IDE is missing, feel free to add a plugin for it and send me a pull request. ;)
-
Autolinks: URLs are rendered as links automatically.
-
Definition lists: Extended syntax for definition lists:
Term : Definition of the term. -
Fenced code blocks: Fenced code blocks as known from GitHub:
```java public class FencedCodeBlock { public void cool() { // do something } } ```If no language is specified, no syntax highlighting will be applied to the code block (except if
-enable-auto-highlightwas specified on the command line, in which case the highlighter will try to guess the language). -
Smartypants: Typographic quotes, en- and em-dashes, ellipsis.
-
Tables: Extended syntax for tables:
Foo | Bar ----|---- A | B C | D -
Wiki-style links: Prettier syntax for links:
[[http://www.google.com Link Title]]Warning: Version 1.2 of this doclet will redefine Wiki-Style links (see issue #7). It's recommended not to use them for now.