From dev-return-19698-archive-asf-public=cust-asf.ponee.io@aries.apache.org Fri Feb 16 09:25:10 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 8919A180647 for ; Fri, 16 Feb 2018 09:25:09 +0100 (CET) Received: (qmail 79938 invoked by uid 500); 16 Feb 2018 08:25:08 -0000 Mailing-List: contact dev-help@aries.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aries.apache.org Delivered-To: mailing list dev@aries.apache.org Received: (qmail 79922 invoked by uid 99); 16 Feb 2018 08:25:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Feb 2018 08:25:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 0581CC01A9 for ; Fri, 16 Feb 2018 08:25:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id BocZlO4yzJ69 for ; Fri, 16 Feb 2018 08:25:07 +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 750D15F576 for ; Fri, 16 Feb 2018 08:25:06 +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 C752FE02AC for ; Fri, 16 Feb 2018 08:25:04 +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 D317721E62 for ; Fri, 16 Feb 2018 08:25:01 +0000 (UTC) Date: Fri, 16 Feb 2018 08:25:01 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: dev@aries.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ARIES-1009) BlueprintContainerImpl - Add INFO logging when the blueprint container has been created 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/ARIES-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366705#comment-16366705 ] ASF subversion and git services commented on ARIES-1009: -------------------------------------------------------- Commit 1824428 from [~gnt] in branch 'aries/trunk' [ https://svn.apache.org/r1824428 ] [ARIES-1009] BlueprintContainerImpl - Add INFO logging when the blueprint container has been created > BlueprintContainerImpl - Add INFO logging when the blueprint container has been created > --------------------------------------------------------------------------------------- > > Key: ARIES-1009 > URL: https://issues.apache.org/jira/browse/ARIES-1009 > Project: Aries > Issue Type: Improvement > Components: Blueprint > Affects Versions: 1.0 > Reporter: Claus Ibsen > Priority: Minor > Fix For: blueprint-core-1.10.0 > > > I am looking into an issue with reload() on aries blueprint, and needed to turn on DEBUG logging on various packages to see what goes on. > What I am missing is also at normal usage an INFO logging that logs when the blueprint container has been created. > eg in BlueprintContainerImpl, you have this code > {code} > eventDispatcher.blueprintEvent(new BlueprintEvent(BlueprintEvent.CREATED, getBundleContext().getBundle(), getExtenderBundle())); > state = State.Created; > {code} > I suggest to add a INFO logging with details about the blueprint container has been created. > Then people can easier spot that the container has been created in their logs. Now you need to enable DEBUG log and look for BlueprintEventDispatcher when it sends the even for CREATED. -- This message was sent by Atlassian JIRA (v7.6.3#76005)