I wonder why that is.

We would have to ask the original author, @stawirej.

It is quite possible that there isn't really a specific reason, but that things just happened to end up this way.

Are there any conceivable downsideds to removing the constraint? Of not, I could update the .zip file.

I haven't found any downsides yet.

Side note: https://github.com/plantuml-stdlib/C4-PlantUML?tab=readme-ov-file#prerequisites mentions PlantUML integration as a prerequiste. The templates work just fine using the IntelliJ AsciiDoc Plugin instead.

I'm guessing that the AsciiDoc integration comes with its own PlantUML. We could update the docs to reflect this, though.

Hi @marcelstoer,

What I found out is that https://github.com/asciidoctor/asciidoctor-intellij-plugin has already a PlantUML support and therefore I assume you don't need the PlantUML integration anymore.

I don't have IntelliJ on my machine.

Can you

• upload a new version of the *.zip without the <option name="AsciiDoc" value="false" />

• retest it only with the PlantUML Integration plugin too
  (without your used AsciiDoc Integration plugin; I assume you use this)

• and add your used configuration as an alternative prerequisite to the README.md?

I would then merge your PR.

Thank you
Helmut