[
https://issues.apache.org/jira/browse/MDEP-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453449#comment-17453449
]
Paul Barton commented on MDEP-774:
----------------------------------
This should work if the maven-dependency-analyzer pushes the 1.12.0 release and
the maven-dependency-plugin pom is updated to use this new version, correct?
As from what I can tell is that the maven-dependency-analyzer 1.11.3 uses
Opcodes.ASM8 (524288) for the API version when initializing the ClassVisitor,
but the latest master has this corrected,
[https://github.com/apache/maven-dependency-analyzer/blob/a79910e73809f45c6cba473d87f880012be7146e/src/main/java/org/apache/maven/shared/dependency/analyzer/asm/DefaultClassVisitor.java#L64]
My understanding is the maven-dependency-plugin 3.2.0 (latest version) uses ASM
9.1 which will fail with this error if the API version when initializing
ClassVisitor is less than Opcoes.ASM9 (589824),
[https://gitlab.ow2.org/asm/asm/-/blob/ASM_9_1/asm/src/main/java/org/objectweb/asm/ClassVisitor.java#L265]
> analyze-only failed: PermittedSubclasses requires ASM9
> ------------------------------------------------------
>
> Key: MDEP-774
> URL: https://issues.apache.org/jira/browse/MDEP-774
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
> Affects Versions: 3.2.0
> Environment: Maven 3.8.2, Adoptium 17, MacOS 11.6
> Reporter: Dan Ziemba
> Assignee: Sylwester Lachiewicz
> Priority: Critical
> Fix For: next-release
>
>
> The analyze-only goal does not work with Java 17 bytecode:
> {noformat}
> Execution dep-analyze of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.2.0:analyze-only failed:
> PermittedSubclasses requires ASM9{noformat}
> Running the same build under the same version of Java 17, but with
> "maven.compiler.release" set to 16 works fine.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
