-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
weird issue with snakeyaml #101
Comments
I tried using other libs, or using different class in snakeyam. result is, issue only appears snakeyaml v2.0+ and with other classes in that lib too.
When I switch to snakeyaml v1.33 all tests pass ; when I switch to 2.0
|
Is it with head revision or the 3.x version? |
jcodemodel version is 3.4.1 I keep that class in my compiler to be sure the snakeyaml version allows to compile( when there is a huge number of classes to compile, I don't want it to fail at compile time) |
Note that it could as well be an issue with my own dynamicClassLoader code. I tried to find it in your source but could not :'( :'( :'( though I remembered having submitted a patch in that regard. |
Yes I know - I didn't do much in this project lately - and the proposed changes were so huge I couldn't understand them properly without investing more time. |
I checked and there was no update here https://mvnrepository.com/artifact/com.helger/jcodemodel (I just spent a lot of time merging all my dependencies management in the same pom) |
sakeyaml uses java17 (which was specified in my projet java.version=17 ). |
Snakeyaml 2.2 uses 1.7 according to https://search.maven.org/artifact/org.yaml/snakeyaml/2.2/bundle |
Sorry can't help you out in any more detail - I an in front of a 4 week leave and need to finish tons of other things first :( Back in November. Good luck |
No problem :) java17 is the version specified in the root pom. Now java 21 :
This is the newish (3years now?) way to specify java version
Still same errors :
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The following test class
fails on snakeyaml dependency 2.0 or 2.3 .
It however passes on snakeyaml 1.33 , which has critical security issues
I checked and snakeyaml is not imported with the dependencies (besides testng). If I do a main the same problem arises.
It may be a problem with my dynamic classloader, or the way the class is available in the jar (require module ?)
The text was updated successfully, but these errors were encountered: