Hi Toni, Le 29/09/2024 à 01:37, Toni Mueller a écrit :
Hi Pierre, On Sat, Sep 28, 2024 at 11:30:34PM +0200, Pierre Gruet wrote:I also think we should not target only Groovy 3; maybe 4, or even 5 if we are not in a hurry. However, a quick glance at the sources shows that there are .groovy files to compile in the source of groovy, so jumping from the current 2.x to 5 (or even 4?) is certainly an important technical challenge.I would aim at installing a new version of Groovy independently of the existing Groovy 2.x package, so the user should be able to choose which one the user wants and smoothly transition. In addition, there could be, in analogy to the earlier situation in the Python area, a "groovy-is-grovy2" or a "groovy-is-groovy4" package to configure a system-wide preference.
OK I see!
How do you think we should start? Maybe creating a new branch in the Salsa repo of groovy?I am inclined to try to start over because at least I could already not incorporate the changes required for Groovy3. I guess the changes required for Groovy4 or -5 would be even bigger. As I said initially, I'm not a Java developer at all, so I'll definitely need some help here.
I have worked on groovy3 and settled a git repo at https://salsa.debian.org/java-team/groovy3with my work. I started from the packaging of groovy (hence some leftover files that we will remove or modify later in the debian/ directory), I updated dependencies and the Maven rules to find them. Now I am running into antlr issues in the ensureGrammars target, but hopefully this is just a missing jar of classpath info and we can go ahead soon with it.
I let you have a look if you wish and I can go on later.
Kind regards, Toni
Cheers, -- Pierre
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature