Dridi Boukelmoune wrote:
> I think it boils down to having people to do the work, which is
> probably not an easy task. I'm also assuming we'd need a more
> up-to-date gradle package, which might not be a trivial task, and I
> suspect that the build system is probably full of "Fedora violations"
> between the need for an internet access, fetching pre-built
> dependencies, bundling some dependencies...
The main issue is that the dependency between Gradle and Kotlin is circular.
Gradle is actually blocking, among other things, on Kotlin being packaged,
and Kotlin is blocking on Gradle (which has been entirely retired because
its maintainers were unable to keep it up to date). See the recent "Package
uses Gradle (retired) to build: what to do?" thread.
Gradle also has a circular dependency of the same kind on its main
implementation language, Groovy.
And of course, Gradle also has a trivial circular dependency on itself.
And finally, there is also Scala code in Gradle now. I am not sure whether
the latest version of Scala can be built without Gradle or whether the
dependency is circular there too.
Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
