Closed klaraward closed 1 year ago
package-info.class
was not deliberately altered, thus it is likely that a change in the Maven plugin version caused this oddity.
I have the same issue with version 1.7.2 and SBT. However I cannot easily exclude it.
In one of our projects use the extra maven enforcer rule
enforceBytecodeVersion
to ensure that artifacts we believe to be JDK 8 compliant actually are.This fails when running against threeten-extra 1.7.1:
We can get around this with exclusions I noticed that the package-info.class files are not in the 1.7.0 jar file, but they are included in 1.7.1 with bytecode version 53. Is this intentional?