Abel Salgado Romero

> The main problem with it is that it's a patch of the asciidoc tool to set properties of a plugin That's pretty much what the plugin does; iterate over...

I am really glad to have this kind of conversations to expand the plugin beyond pure Asciidoctor. But you'll have to help me here because I have some doubts. 1....

Ooook...the thing is being able to run velocity macros using the doxia syntax.

Being completely honest here, no progress done and based on the last conversation, not in immediate roadmap. I am wondering is could be achieved running another plugin previous to the...

> Is this still a desired behavior today? At least to detect breaking changes for sure, for starters, we could have an upstream pipeline that installs asciidoctorj from source in...

> I believe you need to use [asciidoctor-mathematical](https://docs.asciidoctor.org/asciidoctor/latest/stem/mathematical/). Yes, PDF rendering has different requirments. @klvnsa you can find more details in https://docs.asciidoctor.org/pdf-converter/latest/stem/. For questions, I'd suggest dropping them at http://chat.asciidoctor.org/,...

After checking https://github.com/asciidoctor/asciidoctorj/pull/1228 I think we could narrow branch v2.5.x with (note it excludes asciidoctorj-diagram) ``` version: 2 updates: - package-ecosystem: "gradle" directory: "/" schedule: interval: "weekly" labels: - "dependencies"...

Hard to recall all the conversation but we wanted to have typed cleaner methods that was more Java like and less like a simple Ruby wrapper. You should still be...

Working on removing the `@Deprecated` methods for v3.0.x I want to maintain the minimum for this. So far I was thinking in maintaining the methods that return the underlying `Map`,...

Answering https://github.com/asciidoctor/asciidoctorj/pull/1223#discussion_r1239803321 > Generally, testing the compatibility can be quite difficult, to me it means more than the API compiles, and writing integration tests that cover every possible use case...