You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sylwester Lachiewicz (Jira)" <ji...@apache.org> on 2024/03/30 23:22:00 UTC

[jira] [Closed] (MSHADE-461) multi-release jars with java 22 classes cause class version issues

     [ https://issues.apache.org/jira/browse/MSHADE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylwester Lachiewicz closed MSHADE-461.
---------------------------------------
    Resolution: Fixed

> multi-release jars with java 22 classes cause class version issues
> ------------------------------------------------------------------
>
>                 Key: MSHADE-461
>                 URL: https://issues.apache.org/jira/browse/MSHADE-461
>             Project: Maven Shade Plugin
>          Issue Type: Improvement
>            Reporter: PJ Fanning
>            Priority: Major
>             Fix For: 3.5.2
>
>
> See https://github.com/FasterXML/jackson-core/commit/d28275d31f82e8d65e83e5509956789fb4207327
> fastdoubleparser 1.0.0 includes a META-INF/versions/22 directory
> maven-shade-plugin does not support class version 66 (relates to classes built with JDK 22)
> I know Java 22 is still in early access mode but this still allows lib maintainers to include java 22 classes in their multi-release jars.
> Would it be possible to ignore the class version or code defensively so that maven-shade-plugin can workaround it when class version is a little ahead?
> To reproduce the issue, try to build https://github.com/FasterXML/jackson-core (2.17 branch, the default) but remove this line from the pom.xml:
> <exclude>META-INF/versions/22/**/*.*</exclude>



--
This message was sent by Atlassian Jira
(v8.20.10#820010)