polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niclas Hedhman (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ZEST-50) Make the bytecode generation 'pluggable'
Date Thu, 21 Apr 2016 01:09:25 GMT

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

Niclas Hedhman resolved ZEST-50.
       Resolution: Fixed
         Assignee: Niclas Hedhman
    Fix Version/s: 3.0

This can now be done via a custom AssemblyHelper, which is installed via metaInfo in the ApplicationAssembly.

Documentation has be updated with a small blurb about how to do that in the Runtime section,
pointing out that IF someone wants to use this, that they should contact dev@zest.apache.org

> Make the bytecode generation 'pluggable'
> ----------------------------------------
>                 Key: ZEST-50
>                 URL: https://issues.apache.org/jira/browse/ZEST-50
>             Project: Zest
>          Issue Type: New Feature
>            Reporter: Paul Merlin
>            Assignee: Niclas Hedhman
>              Labels: bytecode, core, extensions
>             Fix For: 3.0
>         Attachments: zest-android-screenshot.png
> Dalvik VM has a different bytecode set than Java, and it would be nice to allow the byte
code generation (now in FragmentClassloader and TransientClassloader) to be fully pluggable
to support Android in the future.
> What about ASMDEX or DexMaker ?
> See https://github.com/eskatos/qi4j-android-sample-app

This message was sent by Atlassian JIRA

View raw message