Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 98475 invoked from network); 9 Oct 2009 13:16:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Oct 2009 13:16:57 -0000 Received: (qmail 41531 invoked by uid 500); 9 Oct 2009 13:16:56 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 41445 invoked by uid 500); 9 Oct 2009 13:16:56 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 41202 invoked by uid 99); 9 Oct 2009 13:16:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Oct 2009 13:16:55 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Oct 2009 13:16:52 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6F679234C1EF for ; Fri, 9 Oct 2009 06:16:31 -0700 (PDT) Message-ID: <86123607.1255094191438.JavaMail.jira@brutus> Date: Fri, 9 Oct 2009 06:16:31 -0700 (PDT) From: "Stefan Seelmann (JIRA)" To: dev@directory.apache.org Subject: [jira] Updated: (DIRSTUDIO-155) Logging capabilities needed In-Reply-To: <5781625.1184874306416.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DIRSTUDIO-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSTUDIO-155: -------------------------------------- Fix Version/s: (was: 1.5.0) 2.0.0 Postponed once more. First we need to define which logging framework we should use. ATM we mostly use . Pierre-Arnaud and I already started a discussion about it. Some options: - Eclipse ILog interface provided by each Eclipse plugin - OSGi Log Service - a third-party framework like log4j And should we create our own wrapper, to not depend on the underlying logging framwork? > Logging capabilities needed > --------------------------- > > Key: DIRSTUDIO-155 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-155 > Project: Directory Studio > Issue Type: New Feature > Components: studio-rcp > Affects Versions: 0.8.0 > Environment: Windows XP SP2 German Edition, JDK 1.5.0_10 > Reporter: Markus Pohle > Fix For: 2.0.0 > > > LDAP Studio needs logging capabilities like ApacheDS has. Would really expreciate this for future releases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.