feat: add autodocBom task to generate Autodoc manifests for BOMs #282
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.
What this PR changes/adds
Enables the autodoc functionality for BOM modules. To do that, simply invoke:
or
then, after locally resolving all autodoc manifests of referenced modules, the
autodocBom
task puts the merged manifest inbuild/edc.json
Why it does that
the normal
autodoc
task doesn't work on BOM modules because they typically don't contain code, thus the compiler isn't engaged, andautodoc
doesn't run.Further notes
autodocBom
task is invoked on a project where the name doesn't end with"-bom"
, a warning is loggedresolveManifest
anddownloadManifest
tasks don't generate empty files anymore (null
instead ofInputStream.nullStream()
)Linked Issue(s)
Closes # <-- insert Issue number if one exists
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.