aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raymond Augé (Jira) <j...@apache.org>
Subject [jira] [Commented] (ARIES-1978) Do not embed ASM in SPIFly
Date Mon, 25 May 2020 15:34:00 GMT

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

Raymond Augé commented on ARIES-1978:
-------------------------------------

The dynamic.bundle does not embed ASM, however the dynamic.framework.extension does since
it cannot have package imports.

> Do not embed ASM in SPIFly
> --------------------------
>
>                 Key: ARIES-1978
>                 URL: https://issues.apache.org/jira/browse/ARIES-1978
>             Project: Aries
>          Issue Type: Bug
>          Components: SPI Fly
>    Affects Versions: spifly-1.2.3
>            Reporter: Simone Bordet
>            Assignee: Raymond Augé
>            Priority: Major
>             Fix For: spifly-1.3.0
>
>
> SPIFly embeds ASM at a specific version.
> Given the rapid train of major Java releases, ASM is updated every 6 months to stay up-to-date
with new Java versions, and so SPIFly as well needs to be updated every 6 months because it
embeds ASM.
> Would be great if SPIFly would not embed ASM, so that it can be updated less often than
every major Java releases.
> Projects that consume SPIFly (such as Jetty) will be able to update the SPIFly version
and the ASM version independently.
> See also ARIES-1976.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message