Re: Gradle packaging status update
hello Markus and everyone else,
Markus Koschany <apo@debian.org> writes:
> Am Samstag, dem 20.08.2022 um 18:27 +0200 schrieb Thorsten Glaser:
>> On Sat, 20 Aug 2022, Phil Morrell wrote:
>>
>> > Hi all, documenting my observations as of today because it's not looking
>> > promising for bookworm.
>> >
>> > * kotlin FTBFS because of changes to support openjdk 17 #1012214
>>
>> If gradle depends on kotlin, it’s not eligible for stable anyway
>> because kotlin currently depends on two unsupported JDKs that are
>> available in unstable for bootstrapping and (old…‑)stable support
>> but nothing else.
>
> I agree, help with Kotlin would be really appreciated. At some point it started
> to FTBFS and this should be the first point of investigation. After that we
> should try to package a newer version that builds with and supports Java 17.
>
> I'm making only slow progress with Gradle 6.x because of the long feedback loop
> (changing something, rebuilding and testing takes forever) but the goal is
> still to replace Grade 4.
thank you!
> My conclusion so far is that Debian would be better off if we started to use
> different build systems whenever possible. Most of the time it would be a
> realistic task because many projects upload their artifacts to maven.org and we
> could port those Gradle projects to Maven based projects. I have started to
> work on a few projects and sometimes you could really just use javahelper to
> build an artifact and in the end building from source is the only thing we
> need.
>
> Gradle might be a fantastic tool for visual and GUI driven developers and large
> projects which also use it as a project management tool. In Debian we just need
> something to build source code from the command line and Gradle is simply
> overkill in this regard.
I can speak for Freeplane and as an ex-java-Developer: Gradle is used
for complex build systems, and I like it because it allows scripting via
groovy (with my limited knowledge of maven, you have to add a plugin for
_many_ things).
For Freeplane there are many quirks and fixes in gradle and it would be
very hard to map all these (ok, some things like generating installers
are not needed for a Debian build) to i.e. maven. It would be easier
to downport to gradle4, but even that is far from being easy (you need
to track errors that do not occur in upstream which may be subtle).
That's why I do not have the resources to package freeplane on my own.
Not having gradle is a pity for d-java, and anyway, thanks for the
effort you all put into it!
Cheers and Best Regards,
Felix
--
Felix Natter
Reply to: