Mailing-List: contact clerezza-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: clerezza-dev@incubator.apache.org
Message-ID: <24520883.111731294075608616.JavaMail.jira@thor>
Date: Mon, 3 Jan 2011 12:26:48 -0500 (EST)
From: =?utf-8?Q?Reto_Bachmann-Gm=C3=BCr_=28JIRA=29?= <jira@apache.org>
To: clerezza-dev@incubator.apache.org
Subject: [jira] Closed: (CLEREZZA-205) Logging and profiling capability
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CLEREZZA-205?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Reto Bachmann-Gm=C3=BCr closed CLEREZZA-205.
---------------------------------------

    Resolution: Fixed

> Logging and profiling capability
> --------------------------------
>
>                 Key: CLEREZZA-205
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-205
>             Project: Clerezza
>          Issue Type: New Feature
>            Reporter: Fabian Wabbel
>            Assignee: Reto Bachmann-Gm=C3=BCr
>         Attachments: net.getunik.clerezza.core.logger.zip
>
>
> Hi,
> For our production systems we would like to write log files instead of se=
nding the log to system.out. Any idea what it needs to make this available =
systemwide? I'm dreaming of a Confluence-style configuration: http://i43.ti=
nypic.com/mhgz5.jpg
> Oli has created a first version, would you mind having a look?
> Thanks
> Fabian

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.