[
https://issues.apache.org/jira/browse/FLINK-19513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212384#comment-17212384
]
Matthias edited comment on FLINK-19513 at 10/13/20, 10:17 AM:
--------------------------------------------------------------
I figured out that the regeneration trigger is actually working. The problem
seems to be IntelliJ - maybe that's related to some caches? Editing a file in
IntelliJ won't trigger regeneration. Using {{vi}} instead works as expected.
[~chesnay] Are you using IntelliJ for changing Markdown files of the {{./docs}}
folder?
was (Author: mapohl):
I figured out that the regeneration trigger is actually working. The problem
seems to be IntelliJ - maybe that's related to some caches? Editing a file in
IntelliJ won't trigger regeneration. Using `vi` instead works as expected.
[~chesnay] Are you using IntelliJ for changing Markdown files of the `./docs`
folder?
> Update docs/build_docs.sh to support the new parameters for regenerating the
> docs
> ---------------------------------------------------------------------------------
>
> Key: FLINK-19513
> URL: https://issues.apache.org/jira/browse/FLINK-19513
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
> Reporter: Matthias
> Assignee: Kyle Zhang
> Priority: Minor
> Labels: pull-request-available, starter
>
> I came across Jekyll's regeneration feature not working anymore. After doing
> some research I found [this
> thread|https://github.com/jekyll/jekyll/issues/2926] stating that
> {{--force_polling}} should work. A test confirmed that the regeneration takes
> place with this parameter enabled.
> The {{--watch}} parameter seems to be obsolete.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
