You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Seelmann (JIRA)" <ji...@apache.org> on 2009/10/09 15:16:31 UTC

[jira] Updated: (DIRSTUDIO-155) Logging capabilities needed

     [ 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.