Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8D282200D02 for ; Fri, 8 Sep 2017 18:41:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8C1B91609BE; Fri, 8 Sep 2017 16:41:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D072B1609C0 for ; Fri, 8 Sep 2017 18:41:04 +0200 (CEST) Received: (qmail 91216 invoked by uid 500); 8 Sep 2017 16:41:03 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 91205 invoked by uid 99); 8 Sep 2017 16:41:03 -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; Fri, 08 Sep 2017 16:41:03 +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 1D19C1A0AC8 for ; Fri, 8 Sep 2017 16:41:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id hbCrEK5RgIFc for ; Fri, 8 Sep 2017 16:41:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id A9CD45F569 for ; Fri, 8 Sep 2017 16:41: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 EA63FE0EDB for ; Fri, 8 Sep 2017 16:41: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 36FA72415D for ; Fri, 8 Sep 2017 16:41:00 +0000 (UTC) Date: Fri, 8 Sep 2017 16:41:00 +0000 (UTC) From: "Johannes Utzig (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (KARAF-5356) feature:install fails if log4j has a fragment attached MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 08 Sep 2017 16:41:05 -0000 Johannes Utzig created KARAF-5356: ------------------------------------- Summary: feature:install fails if log4j has a fragment attached Key: KARAF-5356 URL: https://issues.apache.org/jira/browse/KARAF-5356 Project: Karaf Issue Type: Bug Components: karaf-feature Affects Versions: 4.1.2 Reporter: Johannes Utzig I am facing an issue similar to KARAF-4129 To add a custom appender, I created a fragment for pax-logging-log4j2. We create a custom distribution with this fragment. To make sure the fragment is attached to log4j2, I created a feature for it and added it to the startupFeatures