[
https://issues.apache.org/jira/browse/FINERACT-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18070763#comment-18070763
]
Sandro Martínez Pérez commented on FINERACT-2575:
-------------------------------------------------
Hello [~adamsaghy], I believe the best option here is *Eventloop* and here is
why:
* *Bakdata Avro:* the problem with this plugin basically is that in its
documentation says that it applies another gradle-avro-plugin and adds
dependency support. In my opinion for Fineract this introduces an aditional
layer so it's not the cleanest approach.
* *Martin's Java Code:* for this one I couldn't find an option for
{color:#FF0000}templateDirectory {color}which is required for Fineract's Avro
generation.
That being said, *Eventloop* supports{color:#FF0000} templateDirectory
{color}and it matched our current generation flow after validation in the
build. It is also referenced in AVRO-4223 from the Apache Avro Gradle plugin
work, so it looks like the closest replacement path for the archived plugin.
I have already opened a PR implementing the change. Pls review it any time you
can and let me know if you see any issues.
> Change our current, unmaintained Avro schema generation gradle plugin
> ---------------------------------------------------------------------
>
> Key: FINERACT-2575
> URL: https://issues.apache.org/jira/browse/FINERACT-2575
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Adam Saghy
> Priority: Major
> Labels: beginner, beginner-friendly, gsoc2026
>
> Current gradle plugin which is used to generate classes based on avro schema
> files is unmaintained...
>
> We should find and start using an alternative solution:
> *1. Bakdata Avro*
> [https://plugins.gradle.org/plugin/com.bakdata.avro]
> *2. Eventloop software*
> [https://central.sonatype.com/artifact/eu.eventloopsoftware.avro-gradle-plugin/eu.eventloopsoftware.avro-gradle-plugin.gradle.plugin/versions]
> *3. Martin's Java code*
> [https://github.com/martinsjavacode/avro-gradle-plugin]
>
> We need to investigate which would be the best choice of these and make the
> necessary changes.
>
> *Acceptance criteria*
> * Current avro generation gradle plugin to be changed
> ** Due to EOL and unmaintained
> * The new plugin *must* provide the same functionalities and resulted classes
> ** Requests
> ** Responses
> ** Methods
--
This message was sent by Atlassian Jira
(v8.20.10#820010)