[graalvm-users] Graaljs dependency with ASM
christian.wirth at oracle.com
Tue Jun 25 02:23:50 PDT 2019
we strive for a stable, well tested release, so we rather stayed with a
tested version rather than jump on the newest version, especially for a
library that is used only in specific usecases. That is of course a
trade-off, as newer versions also bring bugfixes. Other sub-projects of
GraalVM have transitioned to ASM 7.0 (or even 7.1) in the meantime.
Graal.js will do that reasonably soon, although there is currently no
ETA for that.
The changelog of ASM 6.2.1 => 7.0 => 7.1 does not include any
spectacular change, so I would assume a newer version should work as
well. However, I am not aware how much ASM strives for compatibility
along versions, and we have not tested that version change ourselves yet.
If manually updating the version does not work for you, please feel free
to open a ticket at https://github.com/graalvm/graaljs/issues so we can
track and discuss there.
Am 19.06.2019 um 18:01 schrieb Carlos Aristu:
> I'm starting to integrate Graaljs in a project I'm working on. Its
> latest version (19.0.0) has a compile dependency on asm library
> version 6.2.1.
> Due to a dependency with another library, I already have the asm
> library present in my project's classpath, but I'm using version 7.0.0.
> Do you know if is there any particular reason why Graaljs depends on
> version 6.2.1 of asm instead of depending on a more recent version? It
> would be any trouble if I use asm-7.0.0 or a newer version instead of
> the actual dependency (6.2.1)?
> Thank you in advance.
>  https://mvnrepository.com/artifact/org.graalvm.js/js/19.0.0
> GraalVM-Users mailing list
> GraalVM-Users at oss.oracle.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the GraalVM-Users