<< Back to previous view

[TLOG-12] Reflection Warnings when using tools.logging Created: 30/Apr/13  Updated: 30/Apr/13

Status: Open
Project: tools.logging
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Defect Priority: Major
Reporter: Trevor Bernard Assignee: Alexander Taggart
Resolution: Unresolved Votes: 0
Labels: None

Attachments: Text File 0001-Fix-TLOG-7-Remove-reflection-warnings.patch    
Waiting On: Trevor Bernard

 Description   

A few of my projects are still reflecting using tools.logging 0.2.6 and slf4j-log4j12 "1.7.2".

lein check produces the following output:

...
Reflection warning, curator_clj/zookeeper.clj:1:1 - reference to field isTraceEnabled can't be resolved.
Reflection warning, curator_clj/zookeeper.clj:1:1 - reference to field isDebugEnabled can't be resolved.
Reflection warning, curator_clj/zookeeper.clj:1:1 - reference to field isInfoEnabled can't be resolved.
Reflection warning, curator_clj/zookeeper.clj:1:1 - reference to field isWarnEnabled can't be resolved.
Reflection warning, curator_clj/zookeeper.clj:1:1 - reference to field isErrorEnabled can't be resolved.
Reflection warning, curator_clj/zookeeper.clj:1:1 - reference to field isErrorEnabled can't be resolved.
...



 Comments   
Comment by Alexander Taggart [ 30/Apr/13 5:37 PM ]

I've made a quick test project: https://github.com/ataggart/reflect-log-test

Cloning that repo, running lein check yields no reflection warnings.

Please provide a way for me to reproduce what you see.

Comment by Trevor Bernard [ 30/Apr/13 5:46 PM ]

Forking that project and will try to find a simple test case that reproduces it.





[TLOG-9] spy macro (or new spy macro) that accepts a message Created: 08/Dec/12  Updated: 08/Dec/12

Status: Open
Project: tools.logging
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Enhancement Priority: Minor
Reporter: Dave Sann Assignee: Alexander Taggart
Resolution: Unresolved Votes: 0
Labels: None


 Description   

I think it might be useful to have spy be able to take a message to be logged in addition to the data. (or have a similar macro showing an optional message instead of the code).

(spy "doing x" (blah))
(spy :doing-x (blah) ; because it is easier to type sometimes

with spy this may conflict with the log-level.

I find this sort of function with a message useful and use it quite often. Much more often than plain logging. Generally - I would't log the code unless it logged file and line number too.






Generated at Sat Apr 19 02:20:49 CDT 2014 using JIRA 4.4#649-r158309.