+1
As a first step: at least we can make sure bundles should run with 8 and 11
together
Regards,
Ashok
On 2022/06/15 15:10:53 Konrad Windszus wrote:
> Hi,
> AFAIK all our Sling bundles still target Java 8. I think for major feature
> updates we could increase this to Java 11 to leverage the ne
On Wednesday, 15 June 2022 17:10:53 CEST Konrad Windszus wrote:
> Hi,
> AFAIK all our Sling bundles still target Java 8. I think for major feature
> updates we could increase this to Java 11 to leverage the newly introduced
> features (https://www.geeksforgeeks.org/java-11-features-and-comparison/,
On Wed, 2022-06-15 at 13:02 -0700, Eric Norman wrote:
> >
> > I think it is time now to do the shift.
> > WDYT?
>
>
> +1, though java 11 only has active support until Sep 2023, so we may
> need
> to begin thinking about the path toward java 17
I agree, we should be Java 17 ready. FWIW, we 'ship
On Wed, 2022-06-15 at 17:10 +0200, Konrad Windszus wrote:
> Hi,
> AFAIK all our Sling bundles still target Java 8. I think for major
> feature updates we could increase this to Java 11 to leverage the
> newly introduced features
> (https://www.geeksforgeeks.org/java-11-features-and-comparison/,
> h
>
> I think it is time now to do the shift.
> WDYT?
+1, though java 11 only has active support until Sep 2023, so we may need
to begin thinking about the path toward java 17
Regards,
-Eric
On Wed, Jun 15, 2022 at 8:10 AM Konrad Windszus wrote:
> Hi,
> AFAIK all our Sling bundles still target
+1
Am Mi., 15. Juni 2022 um 17:10 Uhr schrieb Konrad Windszus :
> Hi,
> AFAIK all our Sling bundles still target Java 8. I think for major feature
> updates we could increase this to Java 11 to leverage the newly introduced
> features (https://www.geeksforgeeks.org/java-11-features-and-comparison
