felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4010) SCR Plugin aborts when scanning a Java 8 class file
Date Mon, 29 Apr 2013 05:50:19 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644288#comment-13644288
] 

Carsten Ziegeler commented on FELIX-4010:
-----------------------------------------

We already have the "inherit" flag, which could be used for this. We could also stop scanning,
if the package of a super class starts with "java.".

Maybe we should rethink this inheritence anyway, as long as the super class is in the same
bundle, everything is fine as the tool knows at build time how the class really looks like.
However as soon as the class is not within the bundle anymore, the class used as deployment
time might be different. And the scr plugin can't tell whether a class is within the bundle
or not (the packaging is done at a later stage). The OSGi annotations from DS do not support
inheritance at all, and this is one of the main reasons for this.
                
> SCR Plugin aborts when scanning a Java 8 class file
> ---------------------------------------------------
>
>                 Key: FELIX-4010
>                 URL: https://issues.apache.org/jira/browse/FELIX-4010
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven SCR Plugin
>    Affects Versions: maven-scr-plugin-1.11.0
>            Reporter: Felix Meschberger
>
> It looks like the ASM library referred to by the SCR plugin is not compatible with Java
8 class file version 52.
> How to reproduce: Use Java 8 to run a maven based project build where at least one of
the @Component annotated classes extend (or implement) a Java 8 runtime provided class, e.g.
java.io.Serializable, in class file version 52.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message