Christian Stettler

Add extension mechanism for custom macro support code

1

In order to allow developers to use additional Confluence macros not officially supported by the Confluence Publisher without increasing the complexity and maintenance efforts of the Confluence Publisher itself, an...

Upgrade and minimized Docker image

2

The current Docker image is still based on OpenJDK 8 and has a size of 433MB (uncompressed) / 116MB (compressed). Consider updating to OpenJDK 11 (as used on the build...

Broken path to include file does not break publishing process

4

In case an AsciiDoc file contains a broken include path using the `include::`-macro, the publishing process does not fail, but only logs a warning: ``` asciidoctor: WARNING: : line 19:...

Consolidate integration tests for plugin-, command line and Docker-based publishing

1

Currently, for each supported approaches for publishing (via Maven plugin, via CLI, via Docker image), all integration tests are duplicated (while already consistently using test containers where useful). These tests...

When including a PlantUML diagram as an image in a page and specifying the width of the image using `[plantuml, embedded-diagram, png, width=20]`, the resulting image is not properly scaled...

see https://asciidoctor.org/docs/user-manual/#links and https://asciidoctor.org/docs/user-manual/#anchors

The Confluence Publisher currently generates additional markup elements that would not be generated when editing the same content in Confluence directly. As a consequence, some styling and spacing is not...

Manually edited pages do not get re-published

5

In case a published page is manually edited in Confluence, but does not change in the documentation source, the page content is not re-published (i.e. the manual changes are not...

Currently, not all pre-defined environment attributes (see https://asciidoctor.org/docs/user-manual/#env-attributes) are replaced when converting AsciiDoc to Confluence pages (e.g. `docname` not).