Rafael Winterhalter

I tried it with Liquibase version 3.5.0 and later and they all have this problem. It does not occur when using `autoIncrement` where Liquibase models the sequencing itself but if...

The module-info.class file needs to be compiled in Java 9, otherwise it won't work. The file is however placed in a sub-folder for multi-release jars. This seems to be an...

That is strange. I will try to look into it once I find some time. Could you try to remove the `module-info.class` from the jar and see if it fixes...

No, they are all built on GitHub Actions using a Java 8 JDK. That is really strange, is this something the Eclipse team can give an explanation on?

Looking at this change set: https://github.com/raphw/byte-buddy/compare/byte-buddy-1.12.9...byte-buddy-1.12.10 I can only guess that this has something to do with updating the Maven Shade plugin. That is the only thing that is involved...

You can use a matcher that finds all field accessed in a method. That should be straight forward? You can match the field's declaring type, for example. Internal variables are...

This likely related to the javac version that was used. There has been a row of bugs related to type annotations, and Byte Buddy fails to parse those as they...

You can do this. If you exclude them by their package prefix, the class will not be resolved. You will need to include this matcher first.

Yes, you would need to define a custom ignore matcher that ignores types of this name before attempting to resolve the type description for any other complex property.

By updating, the error will disappear eventually. Incorrect class files will lead to errors. There is some robustness in Byte Buddy, but generally speaking, errors like that cannot be really...