Fixed: various warnings and errors generated by Gradle and due to outdated/incomplete configuration or incompatible plugins

[jacopoc]

This pull request fixes most of the several warnings and errors that are generated by Gradle, by updating task definitions and by configuring its plugins.

Unfortunately there is still one notable warning that is not fixed, caused by the org.asciidoctor.jvm.convertplugin, whose implementation lags behind and prevents us from upgrading to Gradle 9.0.

The warning message is the following:

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
The StartParameter.isConfigurationCacheRequested property has been deprecated.

If a new version of the plugin is not released soon, we should start considering to remove it and rethink our strategy about Asciidoctor based documentation.

[JacquesLeRoux]

Hi Jacopo,

About org.asciidoctor.jvm.convert, I agree that this project is not much alive. Before doing anything else, I have created an issue to ask when they expect to update in order to work with Gradle 9.

I guess Anahita has used a tool like https://github.com/opendevise/downdoc to migrate the main README.adoc. Despite that, migrating all the AsciiDoc documents (264) may not be a negligible task, notably to review and possibly update. Though the last part would be a good thing.

Also what is so important in Gradle 9 to quickly abandon AsciiDoc in favor of Mardown? Could we not wait for a next release ?

[JacquesLeRoux]

Hi Jacopo,

Also it could seem unrelated, but we should have also wait before definitely removing jsGanttImproved.
I got an answer to the issue I created there in January and it's quite positive, thanks to Mario Mol and Claude Code. I'll handle that where it should.

[JacquesLeRoux]

Hi Jacopo,

If you get some times, I'd appreciate that you answer to my question,TIA