You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "David Bosschaert (JIRA)" <ji...@apache.org> on 2018/07/02 09:28:00 UTC

[jira] [Commented] (ARIES-1814) Solve the start order limitations with SPI Fly

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

David Bosschaert commented on ARIES-1814:
-----------------------------------------

Thanks for offering to help out with this issue [~rotty3000]!

> Solve the start order limitations with SPI Fly
> ----------------------------------------------
>
>                 Key: ARIES-1814
>                 URL: https://issues.apache.org/jira/browse/ARIES-1814
>             Project: Aries
>          Issue Type: Improvement
>          Components: SPI Fly
>            Reporter: Raymond Augé
>            Assignee: Raymond Augé
>            Priority: Major
>
> A couple of aspects to try:
> - create a new SPI Fly artifact which is a framework fragment
> - likely needs to embed ASM and Aries Util
> -- maybe use the bnd instruction {{-conditionalpackage}} (which in maven-bundle-plugin becomes {{<_conditionalpackage>}}, same syntax as Import-Package



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)