You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jordan Zimmerman (Jira)" <ji...@apache.org> on 2019/12/15 15:37:00 UTC

[jira] [Created] (MSHADE-337) Relocation cannot process class file version 58 JARs

Jordan Zimmerman created MSHADE-337:
---------------------------------------

             Summary: Relocation cannot process class file version 58 JARs
                 Key: MSHADE-337
                 URL: https://issues.apache.org/jira/browse/MSHADE-337
             Project: Maven Shade Plugin
          Issue Type: Bug
    Affects Versions: 3.2.1
            Reporter: Jordan Zimmerman
         Attachments: shade-bug.zip

I was playing around with Java 14 and was making a shaded JAR. The shade plugin seems to work fine but if I add a relocation it throws:

{noformat}
java.lang.IllegalArgumentException: Unsupported class file major version 58
{noformat}

Steps to Reproduce:
* Unzip the enclosed attachment
* Make sure Java 14 is installed and JAVA_HOME points at it
* Run `mvn package`

Stacktrace:

{noformat}
Caused by: java.lang.IllegalArgumentException: Unsupported class file major version 58
    at org.objectweb.asm.ClassReader.<init> (ClassReader.java:184)
    at org.objectweb.asm.ClassReader.<init> (ClassReader.java:166)
    at org.objectweb.asm.ClassReader.<init> (ClassReader.java:152)
    at org.objectweb.asm.ClassReader.<init> (ClassReader.java:273)
    at org.apache.maven.plugins.shade.DefaultShader.addRemappedClass (DefaultShader.java:438)
    at org.apache.maven.plugins.shade.DefaultShader.shadeSingleJar (DefaultShader.java:240)
    at org.apache.maven.plugins.shade.DefaultShader.shadeJars (DefaultShader.java:196)
    at org.apache.maven.plugins.shade.DefaultShader.shade (DefaultShader.java:106)
    at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute (ShadeMojo.java:442)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
{noformat}

Notes:
* I tried to make the example as minimal as possible
* The relocation patterns don't see to matter. The issue is in the relocator code opening a JAR dependency I guess



--
This message was sent by Atlassian Jira
(v8.3.4#803005)