Allow setting included sources to run full refresh on change #542
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.
Thank you for opening a pull request and contributing to asciidoctor-maven-plugin!
What kind of change does this PR introduce? (check at least one)
What is the goal of this pull request?
Fix conversion not happending when included sources where modified in
autp-refresh
andhttp
mojo.As discussed in #403 at the end we added a new option available for those mojos to allow users to specify other files to "listen to changes on". On a change or creation, a full rebuild will be done.
Are there any alternative ways to implement this?
Current approach allows users to specify a set of extra sources to monitor.
On change a full rebuild (without copying resources) will happen. A full rebuild is necessary since we don't know which sources are affected.
Are there any implications of this pull request? Anything a user must know?
Discarded because custom filters may interfere with other extensions used by users.
Discarded because configurations that maniputale paths (with basePath for example) and have files with same names may be impossible to properly resolve or we may have to also resort to "full builds".
Is it related to an existing issue?
Finally, please add a corresponding entry to CHANGELOG.adoc