["Request"] use arrow-gradle-config plugins and move to build.gradle.kts

[myuwono]

arrow-integrations will need to be released with the latest arrow-gradle-plugin

[JavierSegoviaCordoba]

@i-walker if everything is working correctly with the latest one, we should consider releasing a final version of arrow gradle config, i.e 0.10.0.

I think Arrow is using the latest correct version so you can check it there in the toml file.

[i-walker]

Agree, can we coordinate whether we should publish 0.10.0 before we release arrow or after cc @raulraja, @nomisRev ?

[nomisRev]

Arrow Gradle Config lives independently of arrow-kt/arrow since we're already using it in multiple projects. If Arrow is currently working correctly, then I'm fine releaing a new minor version of Arrow Gradle config 👍

[i-walker]

0.10.0 is released - releasing.

[myuwono]

@i-walker @nomisRev i just saw retrofit integrations are moved into arrow-core-retrofit, i wonder if jackson integration should also be included there? I'm not sure how things are governed within arrow org. I'm happy to raise a PR to arrow and make that move depending on what arrow crew prefers.

[nomisRev]

@myuwono we were actually thinking of moving it out of the Arrow repo since we want to only have Arrow Core, Arrow Fx Coroutines & Arrow Optics related things there. We've run into the issue in the past that everything was in a single repo, and this was absolutely not beneficial for maintenance or local development.

I'm working on a document to create an Arrow committee, where contributors & active users of Arrow will be invited to voice their thoughts and get to influence decisions. We're still organizing it, but this could be a great topic for it. This could be a topic iff discussion there.

[myuwono]

ahh i see cool that makes sense! thanks @nomisRev

[myuwono]

@i-walker i will need to consult you on this.

[i-walker]

Sure, I'll pick this ticket up as soon as possible. Probably end of this week or next week @myuwono