Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.java > #12823 > unrolled thread
| Started by | Julien Plissonneau Duquène <sre4ever@free.fr> |
|---|---|
| First post | 2024-11-04 14:50 +0100 |
| Last post | 2024-11-27 09:30 +0100 |
| Articles | 10 on this page of 70 — 8 participants |
Back to article view | Back to linux.debian.maint.java
gradle reboot Julien Plissonneau Duquène <sre4ever@free.fr> - 2024-11-04 14:50 +0100
Re: gradle reboot Jérôme Charaoui <jerome@riseup.net> - 2024-11-04 15:10 +0100
Re: gradle reboot Toni Mueller <toni@debian.org> - 2024-11-04 17:00 +0100
Re: gradle reboot sre4ever@free.fr - 2024-11-19 11:10 +0100
Re: gradle reboot -- 2024W47 update sre4ever@free.fr - 2024-11-22 18:30 +0100
Re: gradle reboot -- 2024W48 update sre4ever@free.fr - 2024-12-02 19:50 +0100
Re: gradle reboot -- 2024W49 update sre4ever@free.fr - 2024-12-09 12:10 +0100
Re: gradle reboot -- 2024W49 update Emmanuel Bourg <ebourg@apache.org> - 2024-12-09 14:40 +0100
Re: gradle reboot -- 2024W49 update sre4ever@free.fr - 2024-12-09 19:00 +0100
Re: gradle reboot -- 2024W49 update Hans-Christoph Steiner <hans@at.or.at> - 2024-12-09 19:20 +0100
Re: gradle reboot -- 2024W49 update sre4ever@free.fr - 2024-12-10 10:40 +0100
Re: gradle reboot -- 2024W49 update Matthias Klose <doko@debian.org> - 2024-12-14 10:50 +0100
Re: gradle reboot -- 2024W49 update sre4ever@free.fr - 2024-12-14 11:50 +0100
Re: gradle reboot -- 2024W49 update Matthias Klose <doko@debian.org> - 2024-12-14 13:20 +0100
Re: gradle reboot -- 2024W50 update sre4ever@free.fr - 2024-12-13 19:40 +0100
Re: gradle reboot -- 2024W50 update Emmanuel Bourg <ebourg@apache.org> - 2024-12-14 00:40 +0100
gradle: FI -- reverse dependencies that FTBFS sre4ever@free.fr - 2024-12-17 12:00 +0100
Re: gradle: FI -- reverse dependencies that FTBFS Emmanuel Bourg <ebourg@apache.org> - 2024-12-18 10:00 +0100
Re: gradle reboot -- 2024W51 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2024-12-20 19:20 +0100
Re: gradle reboot -- 2025W02 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-01-10 19:30 +0100
Re: gradle reboot -- 2025W03 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-01-17 19:30 +0100
Re: gradle reboot -- 2025W04 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-01-24 19:20 +0100
Re: gradle reboot -- 2025W04 update Hans-Christoph Steiner <hans@at.or.at> - 2025-01-27 17:10 +0100
Re: gradle reboot -- 2025W04 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-01-27 19:30 +0100
Re: gradle reboot -- 2025W05 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-01-31 19:10 +0100
gradle reboot -- 2025W06 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-02-07 19:50 +0100
gradle reboot -- 2025W07 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-02-14 20:10 +0100
Re: gradle reboot -- 2025W07 update Hans-Christoph Steiner <hans@at.or.at> - 2025-02-19 08:00 +0100
Re: gradle reboot -- 2025W07 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-02-19 09:50 +0100
gradle reboot -- 2025W08 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-02-21 18:20 +0100
gradle reboot -- 2025W09 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-02-28 20:30 +0100
gradle reboot -- 2025W10 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-03-07 18:50 +0100
Re: gradle reboot -- 2025W10 update Emmanuel Bourg <ebourg@apache.org> - 2025-03-10 18:50 +0100
Re: gradle reboot -- 2025W10 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-03-10 19:10 +0100
gradle reboot -- 2025W11 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-03-14 19:50 +0100
gradle reboot -- 2025W12 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-03-21 19:00 +0100
kotlin2 in Debian -- 2025W13 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-03-28 20:00 +0100
Re: kotlin2 in Debian -- 2025W13 update Emmanuel Bourg <ebourg@apache.org> - 2025-03-29 12:40 +0100
Re: kotlin2 in Debian -- 2025W13 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-03-29 13:50 +0100
kotlin2 in Debian -- 2025W14 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-04-04 21:00 +0200
kotlin2 in Debian -- 2025W15 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-04-11 14:20 +0200
kotlin2 in Debian -- 2025W16 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-04-18 19:50 +0200
kotlin2 in Debian -- 2025W17 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-04-25 22:10 +0200
kotlin2 in Debian -- 2025W18 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-05-02 19:50 +0200
Re: kotlin2 in Debian -- 2025W18 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-05-06 18:40 +0200
kotlin2 in Debian -- 2025W19 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-05-09 22:20 +0200
kotlin2 in Debian -- 2025W20 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-05-18 13:50 +0200
kotlin2 in Debian -- 2025W21 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-05-23 20:10 +0200
kotlin2 in Debian -- 2025W22 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-05-30 20:50 +0200
kotlin2 in Debian -- 2025W23 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-06-07 19:20 +0200
kotlin2 in Debian -- 2025W24 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-06-14 19:10 +0200
kotlin2 in Debian -- 2025W25 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-06-20 20:00 +0200
Re: kotlin2 in Debian -- 2025W26 and W27 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-07-01 17:00 +0200
kotlin2 in Debian -- 2025W28 to W30 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-07-27 23:00 +0200
kotlin2 in Debian -- 2025W31 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-08-03 22:00 +0200
kotlin2 in Debian -- 2025W32 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-08-11 00:10 +0200
kotlin2 in Debian -- 2025W33 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-08-16 15:40 +0200
kotlin2 in Debian -- 2025W34 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-08-24 17:50 +0200
kotlin2 in Debian -- 2025W35 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-09-01 21:30 +0200
kotlin2 in Debian -- 2025W36 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-09-07 21:50 +0200
kotlin2 in Debian -- 2025W37 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-09-15 14:30 +0200
kotlin2 in Debian -- 2025W38 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-09-22 15:50 +0200
Re: kotlin2 in Debian -- 2025W39-W41 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-10-12 23:10 +0200
Re: kotlin2 in Debian -- 2025W39-W41 update Hans-Christoph Steiner <hans@at.or.at> - 2025-10-31 12:10 +0100
Re: kotlin2 in Debian -- 2025W39-W41 update Bastien Roucaries <rouca@debian.org> - 2026-02-15 20:00 +0100
Re: kotlin2 in Debian -- 2025W23 update Emmanuel Bourg <ebourg@apache.org> - 2025-06-16 15:50 +0200
Re: kotlin2 in Debian -- 2025W23 update Julien Plissonneau Duquène <sre4ever@free.fr> - 2025-06-20 21:30 +0200
Re: gradle reboot Emmanuel Bourg <ebourg@apache.org> - 2024-11-08 00:30 +0100
Re: gradle reboot Hans-Christoph Steiner <hans@at.or.at> - 2024-11-26 13:40 +0100
Re: gradle reboot sre4ever@free.fr - 2024-11-27 09:30 +0100
Page 4 of 4 — ← Prev page 1 2 3 [4]
| From | Julien Plissonneau Duquène <sre4ever@free.fr> |
|---|---|
| Date | 2025-09-15 14:30 +0200 |
| Subject | kotlin2 in Debian -- 2025W37 update |
| Message-ID | <Lvgvg-fuUQ-19@gated-at.bofh.it> |
| In reply to | #13060 |
Good day, Sadly this week other concerns sucked all my time and attention and I did not make any significant progress on intellij-community-idea or its dependencies. Thank you Bastien for sponsoring the libjaxen-java upload. I will shortly send a reminder with links for tomorrow's remote meeting, hope to see you there! Cheers, -- Julien Plissonneau Duquène
[toc] | [prev] | [next] | [standalone]
| From | Julien Plissonneau Duquène <sre4ever@free.fr> |
|---|---|
| Date | 2025-09-22 15:50 +0200 |
| Subject | kotlin2 in Debian -- 2025W38 update |
| Message-ID | <LxP5v-hk6B-3@gated-at.bofh.it> |
| In reply to | #13061 |
Good day, Another week went by with no progress on intellij-community-idea and its dependencies as other things kept me busy. Here are some upstream news however: Gradle 9.1.0 was released last Thursday [1] and is the first release to officially support Java 25 for running the build tool. Last week I forgot to mention that Kotlin 2.2.20 was released on 2025-09-10 [2], and this release still doesn't support Java 25 bytecode. Cheers, [1]: https://docs.gradle.org/9.1.0/release-notes.html [2]: https://kotlinlang.org/docs/whatsnew2220.html -- Julien Plissonneau Duquène
[toc] | [prev] | [next] | [standalone]
| From | Julien Plissonneau Duquène <sre4ever@free.fr> |
|---|---|
| Date | 2025-10-12 23:10 +0200 |
| Subject | Re: kotlin2 in Debian -- 2025W39-W41 update |
| Message-ID | <LFbui-4IT7-3@gated-at.bofh.it> |
| In reply to | #13070 |
Good evening (or morning), There was very little progress again on intellij platform libraries these last three weeks due to being preempted by other concerns and then health issues forcing me to take a break this past week. Overall I could only manage to spend 2 hours on intellij-community-idea on week 39 where I could put some work on the build scripts, and a few minutes this week updating the todo list. “En même temps,” week 40, around 175° further east and 82° further south, Vladimir packaged gradleup-shadow [1] and updated intellij-annotations [2]. [1]: https://launchpad.net/~vpa1977/+archive/ubuntu/gradle8-dependencies/+sourcepub/17617376/+listing-archive-extra [2]: https://launchpad.net/~vpa1977/+archive/ubuntu/gradle8-dependencies/+sourcepub/17617442/+listing-archive-extra My plan for this week is to work on building a recent kotlinx-coroutines (starting from Vladimir's previous work) with the current (old) stack as it is now blocking my progress on intellij-community-idea. Cheers, -- Julien Plissonneau Duquène
[toc] | [prev] | [next] | [standalone]
| From | Hans-Christoph Steiner <hans@at.or.at> |
|---|---|
| Date | 2025-10-31 12:10 +0100 |
| Subject | Re: kotlin2 in Debian -- 2025W39-W41 update |
| Message-ID | <LLVb4-9ncb-17@gated-at.bofh.it> |
| In reply to | #13081 |
Hey Julien, Great to see you're still working on this. Hello from the Reproducible Builds Summit. I was just chatting with Efraim of Guix. They did some work on gradle bootstrapping, in case you haven't seen it, but he said that they have paused, and are following your effort. Also, I talked with some of the people who develop https://github.com/google/oss-rebuild for Google. They also are very interested in your work on bootstrapping Gradle. So I thought this would be a good opportunity to check in again to see if you'd like help to try to get funding for this effort. I have some new ideas. As a reminder, when I chatted with the NLnet people about your proposal they rejected, I was able to clarify the idea to them. Then they said they should have funded it. The key is that they want to see the work focused on bootstrapping Gradle generally, without the emphasis on Debian packaging. The Debian piece of the work can be part of the funding. The story of the funding proposal needs to focus on free software bootstrapping in general. All the best, Hans Julien Plissonneau Duquène: > Good evening (or morning), > > There was very little progress again on intellij platform libraries these last > three weeks due to being preempted by other concerns and then health issues > forcing me to take a break this past week. Overall I could only manage to spend > 2 hours on intellij-community-idea on week 39 where I could put some work on the > build scripts, and a few minutes this week updating the todo list. > > “En même temps,” week 40, around 175° further east and 82° further south, > Vladimir packaged gradleup-shadow [1] and updated intellij-annotations [2]. > > [1]: https://launchpad.net/~vpa1977/+archive/ubuntu/gradle8-dependencies/ > +sourcepub/17617376/+listing-archive-extra > [2]: https://launchpad.net/~vpa1977/+archive/ubuntu/gradle8-dependencies/ > +sourcepub/17617442/+listing-archive-extra > > My plan for this week is to work on building a recent kotlinx-coroutines > (starting from Vladimir's previous work) with the current (old) stack as it is > now blocking my progress on intellij-community-idea. > > Cheers, >
[toc] | [prev] | [next] | [standalone]
| From | Bastien Roucaries <rouca@debian.org> |
|---|---|
| Date | 2026-02-15 20:00 +0100 |
| Subject | Re: kotlin2 in Debian -- 2025W39-W41 update |
| Message-ID | <MoPvA-PUO-31@gated-at.bofh.it> |
| In reply to | #13081 |
[Multipart message — attachments visible in raw view] — view raw
Le dimanche 12 octobre 2025, 23:04:09 heure normale d’Europe centrale Julien Plissonneau Duquène a écrit : Hi Any news of this effort ? Rouca > Good evening (or morning), > > There was very little progress again on intellij platform libraries > these last three weeks due to being preempted by other concerns and then > health issues forcing me to take a break this past week. Overall I could > only manage to spend 2 hours on intellij-community-idea on week 39 where > I could put some work on the build scripts, and a few minutes this week > updating the todo list. > > “En même temps,” week 40, around 175° further east and 82° further > south, Vladimir packaged gradleup-shadow [1] and updated > intellij-annotations [2]. > > [1]: > https://launchpad.net/~vpa1977/+archive/ubuntu/gradle8-dependencies/+sourcepub/17617376/+listing-archive-extra > [2]: > https://launchpad.net/~vpa1977/+archive/ubuntu/gradle8-dependencies/+sourcepub/17617442/+listing-archive-extra > > My plan for this week is to work on building a recent kotlinx-coroutines > (starting from Vladimir's previous work) with the current (old) stack as > it is now blocking my progress on intellij-community-idea. > > Cheers, > >
[toc] | [prev] | [next] | [standalone]
| From | Emmanuel Bourg <ebourg@apache.org> |
|---|---|
| Date | 2025-06-16 15:50 +0200 |
| Subject | Re: kotlin2 in Debian -- 2025W23 update |
| Message-ID | <KYinL-aYxX-1@gated-at.bofh.it> |
| In reply to | #13006 |
Hi Julien, On 07/06/2025 19:14, Julien Plissonneau Duquène wrote: > A significant difference with the current Kotlin package is that I'm > planning to remove (if possible) all embedded copies of libraries. This > will require to patch some of them that were forked by JetBrains to fix > or add features. I'm not sure this is a good idea, because it diverges from upstream, increases the maintenance burden, and could potentially break kotlin if such a dependency gets broken and can no longer compile (due to kotlin being broken). For kotlin I'd recommend keeping it simple and sticking to the upstream layout as much as possible. Saving a few kilobytes isn't important here. Emmanuel Bourg
[toc] | [prev] | [next] | [standalone]
| From | Julien Plissonneau Duquène <sre4ever@free.fr> |
|---|---|
| Date | 2025-06-20 21:30 +0200 |
| Subject | Re: kotlin2 in Debian -- 2025W23 update |
| Message-ID | <KZPAZ-bXEp-17@gated-at.bofh.it> |
| In reply to | #13010 |
Hi Emmanuel, Le 2025-06-16 15:45, Emmanuel Bourg a écrit : > On 07/06/2025 19:14, Julien Plissonneau Duquène wrote: > >> A significant difference with the current Kotlin package is that I'm >> planning to remove (if possible) all embedded copies of libraries. >> This will require to patch some of them that were forked by JetBrains >> to fix or add features. > > I'm not sure this is a good idea, because it diverges from upstream, > increases the maintenance burden, and could potentially break kotlin if > such a dependency gets broken and can no longer compile (due to kotlin > being broken). For kotlin I'd recommend keeping it simple and sticking > to the upstream layout as much as possible. Saving a few kilobytes > isn't important here. I think it would actually be easier terms of maintenance, space savings are definitely not the reason behind that move. I would worry more about the risks of breaking a shared dependency used elsewhere by patching it for kotlin. The alternatives here are to either embed the dependencies in the kotlin package (which is the way it's currently done), or package the JetBrains forks separately. Embedding the dependencies means that the compiler package has to be rebuilt at least twice after patching a dependency: a first time to build an updated package with the old package, then a second time to rebuild the compiler with a compiler that uses the updated dependency. And if there is kotlin-specific patching involved of that dependency, the source package would become multi-tarball again. All these make the package maintenance more complicated and brittle, e.g. if someone else updates an embedded dependency package but forgets to (test-)rebuild the compiler twice afterwards, it might fail to build later at an inconvenient time. Packaging the JetBrains forks separately avoids the issues above, but still adds to maintenance burden as now the forked package has to be maintained in addition to the mainstream package. In most cases the duplication would make no sense IMO. I will consider it though if there is no reasonable way to make the regular dependency package useable with kotlin (by patching either the dependency and/or kotlin). Diverging from upstream is not ideal, but there is such a gap in policies and goals between the binary releases from the upstream projects and Debian that it is completely unavoidable anyway. In several cases, upstream depends on older releases of libraries than those shipped in Debian, probably because they have to provide commercial support on older releases of IDE and tools. My plan is to use the upstream test suites to detect and mitigate issues that could be introduced by Debian divergences, and keep these to a minimum where it actually matters. -- Julien Plissonneau Duquène
[toc] | [prev] | [next] | [standalone]
| From | Emmanuel Bourg <ebourg@apache.org> |
|---|---|
| Date | 2024-11-08 00:30 +0100 |
| Message-ID | <JGk6R-7lLv-7@gated-at.bofh.it> |
| In reply to | #12823 |
Hi Julien, Le 04/11/2024 à 14:43, Julien Plissonneau Duquène a écrit : > This is to let you know that I am currently working on overhauling and > upgrading the gradle package to the upcoming 8.11 release. This is > indeed quite challenging and I am not yet to the point where I could > share a repo and let others experiment and contribute, but I hope to get > there in a few days or maybe next week, I will then post an update with > a link. Thank you for tackling this issue, this challenge requires a lot of time, skills and patience. It's long, thankless, but definitely fun if you are a bit masochistic. > My current plan is to make it at least a 2-stage build as there is no > point in trying to make its complicated buildscript work with the > currently packaged version 4.4.1. I don't know yet if the versions of > Groovy and Kotlin currently in Debian will work with these builds but I > will try. No they won't work. Getting Kotlin 1.3.31 to build with Java 17 was an epic achievement but unfortunately it didn't even allow us to package an incremental update of Gradle. Kotlin and Gradle are tightly coupled, and unless you are ready to rewrite their build systems with something else and replace the Kotlin code in Gradle, I don't think it's possible to bootstrap them separately. That was the motivation behind the gradle-bootstrap package currently in sid: start with a binary only package containing Gradle, Koltin and their dependencies, and use it to gradually rebuild these components from source until the bootstrap package is no longer needed. I haven't pushed further in this direction by lack of time but I still think that's the best strategy to build a recent version of Gradle and Kotlin. Note that there is also an issue with the Gradle enterprise plugin that isn't open sourced and has to be removed. I don't know if Gradle 8 is still affected. > I am also factoring in the gradle-debian-helper in the build > of Gradle itself to use its logic to resolve artifact versions, even > though the plugin can no longer be used as is because it depends on a > core 'maven' plugin that disappeared with Gradle 7. > > About myself, I haven't contributed much to the project yet but I am a > long time FLOSS advocate and Debian user, with some background in large > scale deployments, SRE and DevOps things. I didn't have much prior > experience with Gradle until the past few days, so I am learning while > doing it. If you succeed I predict that you'll be able to add "Kotlin Guru" to your CV:) Good luck! Emmanuel Bourg
[toc] | [prev] | [next] | [standalone]
| From | Hans-Christoph Steiner <hans@at.or.at> |
|---|---|
| Date | 2024-11-26 13:40 +0100 |
| Message-ID | <JN31f-bKOr-23@gated-at.bofh.it> |
| In reply to | #12827 |
Emmanuel Bourg: > Hi Julien, > > Le 04/11/2024 à 14:43, Julien Plissonneau Duquène a écrit : > >> This is to let you know that I am currently working on overhauling and >> upgrading the gradle package to the upcoming 8.11 release. This is indeed >> quite challenging and I am not yet to the point where I could share a repo and >> let others experiment and contribute, but I hope to get there in a few days or >> maybe next week, I will then post an update with a link. > > Thank you for tackling this issue, this challenge requires a lot of time, skills > and patience. It's long, thankless, but definitely fun if you are a bit > masochistic. > > >> My current plan is to make it at least a 2-stage build as there is no point in >> trying to make its complicated buildscript work with the currently packaged >> version 4.4.1. I don't know yet if the versions of Groovy and Kotlin currently >> in Debian will work with these builds but I will try. > > No they won't work. Getting Kotlin 1.3.31 to build with Java 17 was an epic > achievement but unfortunately it didn't even allow us to package an incremental > update of Gradle. > > Kotlin and Gradle are tightly coupled, and unless you are ready to rewrite their > build systems with something else and replace the Kotlin code in Gradle, I don't > think it's possible to bootstrap them separately. > > That was the motivation behind the gradle-bootstrap package currently in sid: > start with a binary only package containing Gradle, Koltin and their > dependencies, and use it to gradually rebuild these components from source until > the bootstrap package is no longer needed. I haven't pushed further in this > direction by lack of time but I still think that's the best strategy to build a > recent version of Gradle and Kotlin. > > Note that there is also an issue with the Gradle enterprise plugin that isn't > open sourced and has to be removed. I don't know if Gradle 8 is still affected. It is great that you are taking this on! It is a very valuable thing to get done. I will try to help and review as I find time, but I'm really slammed at the moment. Another thing I can offer is help with funding for doing this work, if that is interesting to you. Specifically, NLnet's Mobifree fund (https://nlnet.nl/mobifree/) is likely to fund this kind of work because Gradle is so important for Android. And having Gradle in Debian means it truly is free software. I will happily help you put together a proposal for NLnet. The money would then go directly to you. They pay you as a gift from a foundation, and the overall process is relatively easy. .hc
[toc] | [prev] | [next] | [standalone]
| From | sre4ever@free.fr |
|---|---|
| Date | 2024-11-27 09:30 +0100 |
| Message-ID | <JNlAR-bWTW-1@gated-at.bofh.it> |
| In reply to | #12833 |
Hi Hans-Cristoph, Le 2024-11-26 13:37, Hans-Christoph Steiner a écrit : > Another thing I can offer is help with funding for doing this work, if > that is interesting to you. Specifically, NLnet's Mobifree fund > (https://nlnet.nl/mobifree/) is likely to fund this kind of work > because Gradle is so important for Android. And having Gradle in > Debian means it truly is free software. I will happily help you put > together a proposal for NLnet. The money would then go directly to > you. They pay you as a gift from a foundation, and the overall process > is relatively easy. Well it's soon Christmas so I'm not against the funding ^ ^ but it may take a while until the Gradle package in Debian becomes suitable for Android development. I haven't checked that specifically yet but there is probably a bunch of really needed dependencies that would require packaging. My focus for now is first to make Gradle in Debian suitable for rebuilding Debian packages on a CI, second to make it suitable for Debian development using IDEs (IDEA specifically) which wasn't possible out of the box with the packaged Gradle 4.4.1 but I found out how this could be made to work. If the foundation is willing to fund some work as well on packaging dependencies and upgrading Kotlin that may make sense and shift some of my priorities for what comes next after Gradle. You can mail me off-list to work out the details. Cheers, -- Julien Plissonneau Duquène
[toc] | [prev] | [standalone]
Page 4 of 4 — ← Prev page 1 2 3 [4]
Back to top | Article view | linux.debian.maint.java
csiph-web