Closed AHijner closed 7 months ago
@AHijner It's weird...
We are wondering if Charba or Chart.js somehow specify which version of ASM to use?
No, Charba is not using ASM. We don't have any runtime dependencies, because we assume that Charba is leveraging on GWT and its JSInterop annotation implementation. No other dependencies.
Currently I'm using OpenJDK 11 and GWT 2.9 without any issue. It seems you are using IntellJ that I'm not using but I don't think it could be related. Let me do some investigation to understand what could be.
@AHijner I had a look to GWT 2.9.0 dependencies and it has the dependency with ASM 7.1 (https://mvnrepository.com/artifact/com.google.gwt/gwt-dev/2.9.0).
Are you using maven to get the GWT dependencies or the GWT SDK (where ASM is embedded)?
From what I understand, the warnings/errors occur when using the JetBrains GWT plugin in IntelliJ, which indeed seems to have ASM embedded. Most of my team use this method. However, when using maven instead, I indeed don't see the same errors. As the GWT plugin does seem to have ASM 7.x, the error that ASM7 is required still confuses me. Perhaps the exact versions don't match or something. I'll discuss with my team if instead we can all use maven to get the GWT dependencies, or if we would really like to keep using the GWT plugin.
@AHijner thank you very much for feedback! Maybe this link in Google groups could help: https://groups.google.com/g/google-web-toolkit/c/l_E1Y8XKg7k/m/wap_721jBwAJ
@AHijner I think we can close this issue because not strictly related to Charba. Feel free to reopen if needed.
Hi
We're currently running Charba 6.0 after updating some weeks ago. Everything seems to be working alright, except for alot of suppressed errors/warnings we get at startup:
We are using ASM 9.2, changing it to any version of 7.x does not influence these errors, nor does updating Charba to version 6.1 or 6.2. We are wondering if Charba or Chart.js somehow specify which version of ASM to use?
Since our application is running fine otherwise, it's not a huge issue, but it might hide any other future errors from us, so we would like to solve it if at all possible.
Additional info: we are running Java 11 and GWT 2.9.0