Hi Egon,
I'm not really a programmer/developer. Just doing this on the side/as hobby so
it's hard to answer the question.
Personally I would say cdk should only use slf4j and not a specific Logging
library like log4j (maybe already the case?) and come without implementation
and configuration file so that a user can use his own configuration file and
logging library without the cdk affecting it.
For a more specific answer I will need to look at he issue again more closely.
My solution was to just use cdk 1.2.7
Regards,
Thomas
> From: egon.willigha...@gmail.com
> Date: Sat, 12 Feb 2011 15:50:37 +0000
> Subject: Re: [Cdk-user] logging disabled with cdk-1.3.7
> To: beginn...@hotmail.de
> CC: cdk-user@lists.sourceforge.net
>
> Hi Thomas,
>
> the reason why I am replying only now is that I was hoping to come up
> with an answer, but...
>
> On Sat, Dec 4, 2010 at 12:03 PM, Thomas Strunz <beginn...@hotmail.de> wrote:
> > some additional remarks: If I set logging in code to level "warn" then it is
> > displayed but not when using debug. (eg. logger.warn(myMessage) works but
> > not logger.debug(myMessage)).
>
> This was indeed not clear to me at first... it seems the CDK logger
> might overwrite you configuration... so, you might want to have a look
> at 'our' config file:
>
> https://github.com/cdk/cdk/blob/cdk-1.4.x/src/main/org/openscience/cdk/config/data/log4j.properties
>
> Might the first line in that file be the culprit:
>
> log4j.rootCategory=DEBUG, file
>
> Please let me know how we should improve this config file...
>
> Egon
>
> --
> Dr E.L. Willighagen
> Postdoctoral Researcher
> Institutet för miljömedicin
> Karolinska Institutet
> Homepage: http://egonw.github.com/
> LinkedIn: http://se.linkedin.com/in/egonw
> Blog: http://chem-bla-ics.blogspot.com/
> PubList: http://www.citeulike.org/user/egonw/tag/papers
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Cdk-user mailing list
Cdk-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdk-user
