-
Notifications
You must be signed in to change notification settings - Fork 47
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
Failed to enforce bytecode version with JAR which contain module-info.class #46
Labels
Comments
Workaround, ignore <plugin>
<artifactId>maven-enforcer-plugin</artifactId>
<executions>
<execution>
<id>enforce-bytecode-version</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<enforceBytecodeVersion>
<maxJdkVersion>1.7</maxJdkVersion>
<ignoreClasses>
<ignoreClass>module-info</ignoreClass>
</ignoreClasses>
</enforceBytecodeVersion>
</rules>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.codehaus.mojo</groupId>
<artifactId>extra-enforcer-rules</artifactId>
<version>1.0-beta-7</version>
</dependency>
</dependencies>
</plugin> |
Is this covered by #36 ? |
Vlatombe
added a commit
to Vlatombe/extra-enforcer-rules
that referenced
this issue
Mar 20, 2019
darxriggs
added a commit
to darxriggs/jacoco-plugin
that referenced
this issue
Nov 3, 2019
It was originally introduced because the ASM jar files contain a module-info.class which is targeted to Java 9. When using JDK 8 for building the enforcer therefore complained. The current parent pom uses the newer extra-enforcer-rules 1.2 which ignores the module-info.class in case a JDK < 9 is used. For more details see - mojohaus/extra-enforcer-rules#33 - mojohaus/extra-enforcer-rules#46
Does #76 resolve it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Need to think about this situation?
maven-help-plugin in commit without the upgrade to parent 31 it works after upgrade it fails with the following messages:
The question is if we take
module-info.class
as violation for byte code version into account?The text was updated successfully, but these errors were encountered: