------------------------ Guillaume Nodet
Le dim. 25 mai 2025 à 13:30, Elliotte Rusty Harold <elh...@ibiblio.org> a écrit : > > As much as I would like to rip out Modello and chuck it into the > Mariana trench, I don't think that's likely to happen. Why is that so ? If you want to replace it with something else, I’d be fine. We’re mostly using velocity templates, so the two things we’re using from modello now are: the modello model and the xsd generator. But if what you want is get rid of code generation, I don’t see why we would want to add maintenance burden (manually maintaining hundreds of classes) instead of less. Consequently > this is a non-starter. If you do manage to rip out and replace > Modello, then we can talk about record classes, but I don't want to > have both Modello and record classes, which is what would likely > happen if we tried this today. I don’t see why both are related. A single change to the velocity templates (which is in the maven core source code, not modello) would allow the switch. That sounds like a good idea to give it a try to me. > > > > Java 24+ (in a later Maven version) for class-file API. It would resolve > > at least some of the compatibility problems observed when new Java > > versions are released and Maven wants to analyse the byte code. > > This one is interesting. Unfortunately it's far too early to require > Java 24+ for users, which is what we'd need for this, since users > would need to run code that calls this API. I don't want to predict > exactly when this will be possible. However, it's multiple years away. > Most big dev shops are extremely slow to upgrade. 3 years ago when I > left Google, they had just finished a multi-year company wide > migration to Java 11. Meta isn't as big a Java shop, but they too were > using Java 11 at least through late 2024. They and others will > eventually get to Java 25, but that's years in the future. If big shops are slow to upgrade, we don’t have to care about them, as I doubt this is only the case for the JDK. It will also concern Maven, so I don’t see why we should bother taking them into account since they won’t be using Maven 4 before years anyway. > > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
