maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Seweryn Habdank-Wojewodzki (JIRA)" <>
Subject [jira] [Created] (MENFORCER-300) Enforcer somewhat is too sensitive
Date Thu, 29 Mar 2018 14:56:00 GMT
Seweryn Habdank-Wojewodzki created MENFORCER-300:

             Summary: Enforcer somewhat is too sensitive
                 Key: MENFORCER-300
             Project: Maven Enforcer Plugin
          Issue Type: Bug
          Components: Plugin
    Affects Versions: 3.0.0-M1
            Reporter: Seweryn Habdank-Wojewodzki

I am building library with maven settings:

And our customer require that we provide JDK 1.7 compatible SW.

Thanks to the help [How to confiugure maven-enforcer-plugin to exclude some rule in test scope?|]
I had setup:
Compiler plugin settings guarantee that **our** code is 1.7, but enforce plugin proves also

Our library is using Log4j2 v. 2.10.0 and apparently enforce plugin complains that:
    log4j-api:jar:2.10.0:compile contains module-info.class targeted to JDK 1.9
Exactly I got:
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (enforce-bytecode-version) @ clj-log4j2-appender
[INFO] Restricted to JDK 1.7 yet org.apache.logging.log4j:log4j-api:jar:2.10.0:compile contains
module-info.class targeted to JDK 1.9
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion failed with message:
Found Banned Dependency: org.apache.logging.log4j:log4j-api:jar:2.10.0
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
 * our library is working very well on JDK 1.7 with given Log4j 2.10.0
 * dependency tree did not show this module-info, as it is single class and not a package

Is then Enforcerer too sensitive? Handles Enforcerer correctly classes like module-info?

This message was sent by Atlassian JIRA

View raw message