You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/05/25 15:07:00 UTC
[jira] [Commented] (ARIES-1978) Do not embed ASM in SPIFly
[ https://issues.apache.org/jira/browse/ARIES-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116102#comment-17116102 ]
ASF subversion and git services commented on ARIES-1978:
--------------------------------------------------------
Commit 6ae6c1a4ceaded2ce346fc4003e2bbe8d7e6a0cf in aries's branch refs/heads/trunk from Raymond Augé
[ https://gitbox.apache.org/repos/asf?p=aries.git;h=6ae6c1a ]
ARIES-1978 Do not embed ASM in SPIFly
Signed-off-by: Raymond Augé <ro...@apache.org>
> 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
> 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)