There it is https://github.com/apache/deltaspike/pull/96
Looking forward to see 1.9.2 being released with this!
Regard,
Christian
Am 20.08.2019 um 10:17 schrieb Thomas Andraschko:
No plans yet
but the first step would be to create a issue for the update and
provide a PR
Christian Beikov <[email protected]
<mailto:[email protected]>> schrieb am Di., 20. Aug. 2019, 10:01:
That's ok for me. When are you planning to do the next release
(1.9.2?)
with ASM 7.1 that supports Java 13?
Regards,
Christian
Am 20.08.2019 um 09:55 schrieb Thomas Andraschko:
> Hi,
>
> Why should this be easier to update? You would still need to
rebuild/shade
> ASM within a DS package.
> Also also the relation between the ASM proxy and ASM is 1:1.
>
> As not every Java release requires a new ASM, i currently don't
see a
> problem.
> We should just release every 6-12 months.
>
> Best regards,
> Thomas
>
>
> Am Di., 20. Aug. 2019 um 07:00 Uhr schrieb Christian Beikov <
> [email protected] <mailto:[email protected]>>:
>
>> Hey,
>>
>> I'm very happy that Deltaspike 1.9.1 was release a few days
ago, but
>> since releases aren't done very often recently I'd like to get your
>> opinion on an issue that is about introducing a separate
artifact that
>> just contains the shaded ASM artifact:
>> https://issues.apache.org/jira/browse/DELTASPIKE-1358
>>
>> In order to allow using Deltaspike Proxy with newer Java
versions, ASM
>> needs to be updated. I don't expect that you release a new
version of
>> Deltaspike after every Java release, which is why I'd like to
suggest
>> moving the shaded ASM parts to a dedicated artifact that can be
excluded
>> and user-provided if necessary for being able to run with newer
Java
>> versions.
>>
>> Deltaspike 1.9.1 finally allows to run with Java 12 bytecode,
but Java
>> 13 is just around the corner which is currently not supported
because it
>> requires ASM 7.1.
>>
>> Any opinions or suggestions on this?
>>
>> Regards,
>>
>> Christian
>>
>>
