You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2023/10/13 10:19:00 UTC

[jira] [Created] (FELIX-6660) osgicheck-maven-plugin:0.1.0:check fails with "Unable to scan annotations null" with Java 11+

Konrad Windszus created FELIX-6660:
--------------------------------------

             Summary: osgicheck-maven-plugin:0.1.0:check fails with "Unable to scan annotations null" with Java 11+
                 Key: FELIX-6660
                 URL: https://issues.apache.org/jira/browse/FELIX-6660
             Project: Felix
          Issue Type: Improvement
          Components: Tooling
    Affects Versions: osgicheck-maven-plugin 0.1.0
            Reporter: Konrad Windszus


Due to using an outdated ASM library in https://github.com/apache/felix-dev/blob/91432d1a3f08520d5eb75b5c8e3443bb75f7c467/tools/osgicheck-maven-plugin/pom.xml#L93 the following error is emitted when scanning classes with java 10+ bytecode:

{code}
[ERROR] Unable to scan annotations null
{code}

which leads to a build error
{code}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.felix:osgicheck-maven-plugin:0.1.0:check (check-bundle) on project ...: Check detected errors. See log output for error messages.
{code}.

Both ASM should be updated and the error handling be improved to emit a better error message when classes cannot be scanned (including the filename).



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