Fix missing configuration properties in generated docs #223
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit fixes the generated documentation possibly missing
configuration properties files. To fix it, it now applies a
configuration properties plugin to Micronaut modules. This plugin
is responsible for creating tasks which will process the configuration
properties file (for each module) and generate an outgoing configuration
which carries those artifacts.
This makes it possible for the "main" project (the aggregating one) to
depend on those configurations in order to get the generated asciidoc
files. This effectively decouples the producer side from the consumer side,
making it less brittle and less likely to break.
It's worth noting that the same technique should be used
in other parts of the docs plugin, but this will be done later.
Basically there are many tasks which do not declare their inputs
and should be replaced with proper tasks instead. As an example,
the
zipDocs
task didn't declare any input: the consequence isthat it may, or may not contain the right docs depending on what
is called before. This is currently fixed by adding an explicit
dependency, but it should be replaced by implicit task dependencies.
Another benefit is that now all configuration properties tasks are
cacheable, which should make the build faster once we enable the
build cache.