[
https://issues.apache.org/jira/browse/KAFKA-20541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18086503#comment-18086503
]
ASF GitHub Bot commented on KAFKA-20541:
----------------------------------------
muralibasani commented on PR #856:
URL: https://github.com/apache/kafka-site/pull/856#issuecomment-4636160595
> I've just tried with 43 (rebasing your branch on top of markdown) and even
though `generated` is only under `static` it still worked, is it expected?
Yes, that's expected. It will work in both ways.
It adds support for content/en/<v>/generated/ without removing the existing
static/<v>/generated/ path.
static/<v>/generated/ (old way) served by Default static → static mount
content/en/<v>/generated/ (new way) served by the catch-all mount entry.
RM can ship generated/ under either static/<v>/ or content/en/<v>/ and both
work.
> Duplicate generated folder in kafka-site
> ----------------------------------------
>
> Key: KAFKA-20541
> URL: https://issues.apache.org/jira/browse/KAFKA-20541
> Project: Kafka
> Issue Type: Bug
> Components: website
> Reporter: Mickael Maison
> Assignee: Muralidhar Basani
> Priority: Major
>
> We have the generated content under both:
> - content/en/<VERSION>
> - static/<VERSION>
> For example:
> https://github.com/apache/kafka-site/tree/markdown/content/en/42/generated
> https://github.com/apache/kafka-site/tree/markdown/static/42/generated
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
