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 BBC77200CC9 for ; Mon, 17 Jul 2017 15:18:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BA2D7164EBD; Mon, 17 Jul 2017 13:18:04 +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 0CA8F164EB6 for ; Mon, 17 Jul 2017 15:18:03 +0200 (CEST) Received: (qmail 42619 invoked by uid 500); 17 Jul 2017 13:18:02 -0000 Mailing-List: contact dev-help@apex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.apache.org Delivered-To: mailing list dev@apex.apache.org Received: (qmail 42608 invoked by uid 99); 17 Jul 2017 13:18:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2017 13:18:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 4D6671805B2 for ; Mon, 17 Jul 2017 13:18:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id yCQSQ9pshTvb for ; Mon, 17 Jul 2017 13:18: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 DE2F360D92 for ; Mon, 17 Jul 2017 13:18:00 +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 71F90E0069 for ; Mon, 17 Jul 2017 13:18: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 316152475C for ; Mon, 17 Jul 2017 13:18:00 +0000 (UTC) Date: Mon, 17 Jul 2017 13:18:00 +0000 (UTC) From: "Vlad Rozov (JIRA)" To: dev@apex.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (APEXCORE-758) Unify Apex plugin configuration settings MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 17 Jul 2017 13:18:04 -0000 [ https://issues.apache.org/jira/browse/APEXCORE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089809#comment-16089809 ] Vlad Rozov commented on APEXCORE-758: ------------------------------------- Where and how a plugin is applied is internal details of a plugin. An application designer or dev ops may not know where a plugin should be applied and may use incorrect settings/attribute to enable plugin. There is no need to expose that complexity as otherwise, every plugin will need to document how it should be enabled instead of unified way to enable plugins. > Unify Apex plugin configuration settings > ---------------------------------------- > > Key: APEXCORE-758 > URL: https://issues.apache.org/jira/browse/APEXCORE-758 > Project: Apache Apex Core > Issue Type: Improvement > Reporter: Vlad Rozov > > There is no need to have multiple conf key for different types of plugins. Plugins should share the same key like "apex.plugins". If possible, it will be good to have an ability to enable plugins at an application level. -- This message was sent by Atlassian JIRA (v6.4.14#64029)