[wildfly-dev] Multi-release module JARs

[Tristan Tarrant]

On 11/06/2020 10:20, Darran Lofthouse wrote:
> On Thu, Jun 11, 2020 at 9:08 AM Tristan Tarrant <ttarrant at redhat.com 
> <mailto:ttarrant at redhat.com>> wrote:
> 
>     I commented on GitHub, but probably this is more appropriate:
> 
>     I really so no point in building releases with JDK 8 any more:
> 
>     * Using the -release 8 compiler argument produces the correct bytecode
>     and verifies JDK method signature compatibility similar to what animal
>     sniffer did
> 
> 
> To add to this -release produces the correct bytecode, but -target does 
> not so it is important to use the correct one of these.
> 
>     * It acts as an obstacle to the usage of JDK-specific improvements
> 
> 
> As we found out, such as preventing the use of new methods added to 
> SSLEngine and SSLSocket in the most recent Java 8 releases.
> 
>     * Raises awareness about incompatibilities that might happen with newer
>     JDKs.
> 
>     I would even go as far as saying that you should build upstream
>     nightlies with the latest stable JDK (14) even if it isn't an LTS just
>     to validate that last statement.
> 
> 
> Let's not push it ;-) - we already know PicketBox and it's integration 
> will crumble when we get to that version ;-)

Well, the next JDK LTS is only a year away, so I hope you are going to 
kill PB before then :)

Tristan