ARTEMIS-4383 migrate user docs to AsciiDoc
Markdown, which is currently used for user-facing documentation, is good
for a lot of things. However, it's not great for the kind of complex
documentation we have and our need to produce both multi-page HTML and
single-page PDF output via Maven.
Markdown lacks features which would make the documentation easier to
read, easier to navigate, and just look better overall.
The current tool-chain uses honkit and a tool called Calibre. Honkit is
written in TypeScript and is installed via NPM. Calibre is a native tool
so it must be installed via an OS-specific package manager. All this
complexity makes building, releasing, uploading, etc. a pain.
AsciiDoc is relatively simple like Markdown, but it has more features
for presentation and navigation not to mention Java-based Maven tooling
to generate both HTML and PDF. Migrating will improve both the
appearance of the documentation as well as the processes to generate and
upload it.
This commit contains the following changes:
- Convert all the Markdown for the User Manual, Migration Guide, and
Hacking guide to AsciiDoc via kramdown [1].
- Update the `artemis-website` build to use AsciiDoctor Maven tooling.
- Update `RELEASING.md` with simplified instructions.
- Update Hacking Guide with simplified instructions.
- Use AsciiDoc link syntax in Artemis Maven doc plugin.
- Drop EPUB & MOBI docs for User Manual as well as PDF for the Hacking
Guide. All docs will be HTML only except for the User Manual which
will have PDF.
- Move all docs up out of their respective "en" directory. This was a
hold-over from when we had docs in different languages.
- Migration & Hacking Guides are now single-page HTML since they are
relatively short.
- Refactor README.md to simplify and remove redundant content.
Benefits of the change:
- Much simplified tooling. No more NPM packages or native tools.
- Auto-generated table of contents for every chapter.
- Auto-generated anchor links for every sub-section.
- Overall more appealing presentation.
- All docs will use the ActiveMQ favicon.
- No more manual line-wrapping! AsciiDoc recommends one sentence per
line and paragraphs are separated by a blank line.
- AsciiDoctor plugins for IDEA are quite good.
- Resulting HTML is less than *half* of the previous size.
All previous links/bookmarks should continue to work.
[1] https://github.com/asciidoctor/kramdown-asciidoc
2023-07-27 23:45:17 -04:00
|
|
|
= Wildcard Syntax
|
|
|
|
|
:idprefix:
|
|
|
|
|
:idseparator: -
|
|
|
|
|
|
|
|
|
|
Apache ActiveMQ Artemis uses a specific syntax for representing wildcards in security settings, address settings and when creating consumers.
|
|
|
|
|
|
|
|
|
|
The syntax is similar to that used by https://www.amqp.org[AMQP].
|
|
|
|
|
|
|
|
|
|
An Apache ActiveMQ Artemis wildcard expression contains *words separated by a delimiter*.
|
|
|
|
|
The default delimiter is `.` (full stop).
|
|
|
|
|
|
2023-10-12 11:56:41 -04:00
|
|
|
The special characters `#` and `*` also have special meaning and can take the place of a **word**.
|
ARTEMIS-4383 migrate user docs to AsciiDoc
Markdown, which is currently used for user-facing documentation, is good
for a lot of things. However, it's not great for the kind of complex
documentation we have and our need to produce both multi-page HTML and
single-page PDF output via Maven.
Markdown lacks features which would make the documentation easier to
read, easier to navigate, and just look better overall.
The current tool-chain uses honkit and a tool called Calibre. Honkit is
written in TypeScript and is installed via NPM. Calibre is a native tool
so it must be installed via an OS-specific package manager. All this
complexity makes building, releasing, uploading, etc. a pain.
AsciiDoc is relatively simple like Markdown, but it has more features
for presentation and navigation not to mention Java-based Maven tooling
to generate both HTML and PDF. Migrating will improve both the
appearance of the documentation as well as the processes to generate and
upload it.
This commit contains the following changes:
- Convert all the Markdown for the User Manual, Migration Guide, and
Hacking guide to AsciiDoc via kramdown [1].
- Update the `artemis-website` build to use AsciiDoctor Maven tooling.
- Update `RELEASING.md` with simplified instructions.
- Update Hacking Guide with simplified instructions.
- Use AsciiDoc link syntax in Artemis Maven doc plugin.
- Drop EPUB & MOBI docs for User Manual as well as PDF for the Hacking
Guide. All docs will be HTML only except for the User Manual which
will have PDF.
- Move all docs up out of their respective "en" directory. This was a
hold-over from when we had docs in different languages.
- Migration & Hacking Guides are now single-page HTML since they are
relatively short.
- Refactor README.md to simplify and remove redundant content.
Benefits of the change:
- Much simplified tooling. No more NPM packages or native tools.
- Auto-generated table of contents for every chapter.
- Auto-generated anchor links for every sub-section.
- Overall more appealing presentation.
- All docs will use the ActiveMQ favicon.
- No more manual line-wrapping! AsciiDoc recommends one sentence per
line and paragraphs are separated by a blank line.
- AsciiDoctor plugins for IDEA are quite good.
- Resulting HTML is less than *half* of the previous size.
All previous links/bookmarks should continue to work.
[1] https://github.com/asciidoctor/kramdown-asciidoc
2023-07-27 23:45:17 -04:00
|
|
|
|
|
|
|
|
To be clear, the wildcard characters cannot be used like wildcards in a https://en.wikipedia.org/wiki/Regular_expression[regular expression].
|
|
|
|
|
They operate exclusively on *words separated by a delimiter*.
|
|
|
|
|
|
|
|
|
|
== Matching Any Word
|
|
|
|
|
|
|
|
|
|
The character `#` means "match any sequence of zero or more words".
|
|
|
|
|
|
|
|
|
|
So the wildcard `news.europe.#` would match:
|
|
|
|
|
|
|
|
|
|
* `news.europe`
|
|
|
|
|
* `news.europe.sport`
|
|
|
|
|
* `news.europe.politics`
|
|
|
|
|
* `news.europe.politics.regional`
|
|
|
|
|
|
|
|
|
|
But `news.europe.#` would _not_ match:
|
|
|
|
|
|
|
|
|
|
* `news.usa`
|
|
|
|
|
* `news.usa.sport`
|
|
|
|
|
* `entertainment`
|
|
|
|
|
|
|
|
|
|
== Matching a Single Word
|
|
|
|
|
|
|
|
|
|
The character `*` means "match a single word".
|
|
|
|
|
|
|
|
|
|
The wildcard `news.*` would match:
|
|
|
|
|
|
|
|
|
|
* `news.europe`
|
|
|
|
|
* `news.usa`
|
|
|
|
|
|
|
|
|
|
But `news.*` would _not_ match:
|
|
|
|
|
|
|
|
|
|
* `news.europe.sport`
|
|
|
|
|
* `news.usa.sport`
|
|
|
|
|
* `news.europe.politics.regional`
|
|
|
|
|
|
|
|
|
|
The wildcard `news.*.sport` would match:
|
|
|
|
|
|
|
|
|
|
* `news.europe.sport`
|
|
|
|
|
* `news.usa.sport`
|
|
|
|
|
|
|
|
|
|
But `news.*.sport` would _not_ match:
|
|
|
|
|
|
|
|
|
|
* `news.europe.politics`
|
|
|
|
|
|
|
|
|
|
== Customizing the Syntax
|
|
|
|
|
|
|
|
|
|
It's possible to further configure the syntax of the wildcard addresses using the broker configuration.
|
|
|
|
|
For that, the `<wildcard-addresses>` configuration tag is used.
|
|
|
|
|
|
|
|
|
|
[,xml]
|
|
|
|
|
----
|
|
|
|
|
<wildcard-addresses>
|
|
|
|
|
<routing-enabled>true</routing-enabled>
|
|
|
|
|
<delimiter>.</delimiter>
|
|
|
|
|
<any-words>#</any-words>
|
|
|
|
|
<single-word>*</single-word>
|
|
|
|
|
</wildcard-addresses>
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
The example above shows the default configuration.
|