From issues-return-138725-archive-asf-public=cust-asf.ponee.io@maven.apache.org Sat Oct 6 19:05:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id AB88F18061A for ; Sat, 6 Oct 2018 19:05:03 +0200 (CEST) Received: (qmail 85971 invoked by uid 500); 6 Oct 2018 17:05:02 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 85959 invoked by uid 99); 6 Oct 2018 17:05:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Oct 2018 17:05:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 4878D1A02CF for ; Sat, 6 Oct 2018 17:05:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id K2YRksGjc_1g for ; Sat, 6 Oct 2018 17:05:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 1B35F5F3B2 for ; Sat, 6 Oct 2018 17:05:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 81951E0E5D for ; Sat, 6 Oct 2018 17:05:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1C8262476F for ; Sat, 6 Oct 2018 17:05:00 +0000 (UTC) Date: Sat, 6 Oct 2018 17:05:00 +0000 (UTC) From: "Karl Heinz Marbaise (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MENFORCER-300) Enforcer somewhat is too sensitive MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MENFORCER-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MENFORCER-300: ------------------------------------------ Fix Version/s: waiting-for-feedback > Enforcer somewhat is too sensitive > ---------------------------------- > > Key: MENFORCER-300 > URL: https://issues.apache.org/jira/browse/MENFORCER-300 > Project: Maven Enforcer Plugin > Issue Type: Bug > Components: Plugin > Affects Versions: 3.0.0-M1 > Reporter: Seweryn Habdank-Wojewodzki > Priority: Major > Fix For: waiting-for-feedback > > > I am building library with maven settings: > {code:java} > 1.7 > 1.7 > > org.apache.maven.plugins > maven-compiler-plugin > 3.7.0 > > ${jvm.path}/bin/javac > 1.7 > 1.7 > > > {code} > 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?|https://stackoverflow.com/questions/49531075/how-to-confiugure-maven-enforcer-plugin-to-exclude-some-rule-in-test-scope/49534564#49534564] I had setup: > {code:java} > > org.apache.maven.plugins > maven-enforcer-plugin > 3.0.0-M1 > > > enforce-bytecode-version > > enforce > > > > > 1.7 > > test > > > > true > > > > > > org.codehaus.mojo > extra-enforcer-rules > 1.0-beta-7 > > > > {code} > Compiler plugin settings guarantee that **our** code is 1.7, but enforce plugin proves also dependencies. > Our library is using Log4j2 v. 2.10.0 and apparently enforce plugin complains that: > {code:java} > log4j-api:jar:2.10.0:compile contains module-info.class targeted to JDK 1.9 > {code} > Exactly I got: > {code:java} > [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. > {code} > However > * 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 (v7.6.3#76005)