Re: [faces-dev] Minimum Java for Faces 5.0

[Mark Thomas <markt@xxxxxxxxxx>]

Faces has a dependency on EL.

EL has just (within the last hour) moved to a minimum of Java 17 so it 
can support Record.

Mark


On 06/11/2023 10:12, Thomas Andraschko via faces-dev wrote:
> IMO we should not force a impl to build on a specific java version.
>
> If we add spec features, which requires newer java versions, we will of 
> course switch to it and implement this feature.
> But as long this is not the case, MF can just be compiled with Java11 
> until EOL.
>
> Same as with e.g. Servlet or CDI. Why just we not support older versions 
> if it just works OOTB?
>
>
> Am Sa., 4. Nov. 2023 um 21:47 Uhr schrieb Bauke Scholtz via faces-dev 
> <faces-dev@xxxxxxxxxxx <mailto:faces-dev@xxxxxxxxxxx>>:
>
>     All,
>
>     We should definitely go for a minimum of 17 as OpenJDK 11 has
>     already reached EOL at 30 sep 2023 and 17 is the next LTS with
>     planned EOL of 30 sep 2026.
>
>     I'm personally in favor of going to 21 directly as EE11 will support
>     it. But I'm also fine with 17 if MyFaces favors it. Unless we find
>     something really useful for Faces in Java 21. But so far I'm not
>     seeing it. How about we set it to Java 17 for now and watch as Faces
>     5.0 progresses and keep the option open to bump further to 21 if
>     some new useful Faces feature demands it?
>
>     Cheers, B
>
>
>     On Thu, Nov 2, 2023 at 10:00 AM Scott Marlow <smarlow@xxxxxxxxxx
>     <mailto:smarlow@xxxxxxxxxx>> wrote:
>
>
>
>         On Wed, Nov 1, 2023 at 10:08 AM Bauke Scholtz via faces-dev
>         <faces-dev@xxxxxxxxxxx <mailto:faces-dev@xxxxxxxxxxx>> wrote:
>
>             Hi,
>
>             I understood Jakarta EE 11 was going to use Java 21? I was
>             already planning to update the Mojarra repo to use Java 21
>             this weekend.
>
>
>         Some Jakarta EE 11 Specifications such as Concurrency are
>         planning to use Java 21 features.  Is Faces 5.0 planned to use
>         any Java 21 or Java 17 features?
>
>         IMO, it is fine for the Faces 5.0 SPEC API + TCK to be compiled
>         with Java 21 as long as the bytecode is targeted to the version
>         required for the Faces 5.0 feature set.  If Faces 5.0 will only
>         have Java 11 features in its SPEC API, the target bytecode
>         version could be set to Java 11.  Is there some other reason
>         besides the minimum required Faces 5.0 feature set that would be
>         used for choosing the bytecode version target?
>
>         The above applies to all Jakarta EE specifications.  Hope this
>         helps.
>
>         Scott
>
>
>             Cheers, B
>
>             On Wed, Nov 1, 2023 at 9:56 AM Edwin Amoakwa via faces-dev
>             <faces-dev@xxxxxxxxxxx <mailto:faces-dev@xxxxxxxxxxx>> wrote:
>
>                 Hello Volodymyr,
>
>                 Not exactly why Java17 was selected, *but it actually
>                 make sense, giving that Java11 have reached end of life.*
>
>                 Thanks,
>                 Edwin.
>
>                 On Wed, Nov 1, 2023 at 1:37 PM Volodymyr Siedlecki via
>                 faces-dev <faces-dev@xxxxxxxxxxx
>                 <mailto:faces-dev@xxxxxxxxxxx>> wrote:
>
>                     Hello,
>
>                     The project plan states that Faces 5.0 will use Java
>                     SE 17 (or higher) as its minimum Java version. *
>                     *
>
>                     See here:
>                     https://jakarta.ee/specifications/faces/5.0/
>                     <https://jakarta.ee/specifications/faces/5.0/>
>
>                     Will the APIs use Java 17 features? Can someone
>                     provide more background why 17 was selected?  I ask
>                     since MyFaces may want to stay on Java 11.
>
>                     Thank you,
>
>                     Volodymyr
>                     _______________________________________________
>                     faces-dev mailing list
>                     faces-dev@xxxxxxxxxxx <mailto:faces-dev@xxxxxxxxxxx>
>                     To unsubscribe from this list, visit
>                     https://www.eclipse.org/mailman/listinfo/faces-dev
>                     <https://www.eclipse.org/mailman/listinfo/faces-dev>
>
>                 _______________________________________________
>                 faces-dev mailing list
>                 faces-dev@xxxxxxxxxxx <mailto:faces-dev@xxxxxxxxxxx>
>                 To unsubscribe from this list, visit
>                 https://www.eclipse.org/mailman/listinfo/faces-dev
>                 <https://www.eclipse.org/mailman/listinfo/faces-dev>
>
>             _______________________________________________
>             faces-dev mailing list
>             faces-dev@xxxxxxxxxxx <mailto:faces-dev@xxxxxxxxxxx>
>             To unsubscribe from this list, visit
>             https://www.eclipse.org/mailman/listinfo/faces-dev
>             <https://www.eclipse.org/mailman/listinfo/faces-dev>
>
>     _______________________________________________
>     faces-dev mailing list
>     faces-dev@xxxxxxxxxxx <mailto:faces-dev@xxxxxxxxxxx>
>     To unsubscribe from this list, visit
>     https://www.eclipse.org/mailman/listinfo/faces-dev
>     <https://www.eclipse.org/mailman/listinfo/faces-dev>
>
>
> _______________________________________________
> faces-dev mailing list
> faces-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/faces-dev