Hi Jason, On Wed, Jul 4, 2018 at 9:27 PM Jason E Bailey <j...@apache.org> wrote: > ...1. I would not consider using or not using java 8's lambda's a > "programming comfort" > the paradigms introduced with Java 8 such as lambda's and streams > fundamentally > change how the source is written and in my experience results in concise, > easier > to understand code...
I agree! But if you're making a minor change to an existing core bundle it might be better to stick to the current Java version that's used for that bundle, instead of changing just because a few lines look nicer. I guess it's a question of balance between what "minor changes" and "better code" are. The most recent discussion that I found about that is this one https://lists.apache.org/thread.html/0bdd59ec761ec07a3fc35144cf9fa9b318496dbc78958127515799b8@%3Cdev.sling.apache.org%3E where we seemed to have consensus about moving individual bundles to Java 8 (as opposed to making that the default, for now) if that brings tangible benefits. At this point I see two options: a) Continue moving individual bundles as needed, and IMHO it's good to do a 72-hours [LAZY] vote before changing core bundles like engine, API etc. b) Revisit that discussion and make Java 8 the default in the parent pom I don't have strong opinions myself, I just want such decisions to be made explicitly by this PMC and community. -Bertrand
