<< Back to previous view

[TLOG-16] Add ClojureScript support? Created: 21/Jul/16  Updated: 21/Jul/16

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

Type: Enhancement Priority: Major
Reporter: Daniel Compton Assignee: Alexander Taggart
Resolution: Unresolved Votes: 0
Labels: None


 Description   

It would be really neat if there was a unified Clojure/ClojureScript logging library. I'm thinking it would have the same API as the Clojure one. I'm not 100% sure how appenders would work though. Would a patch for this be considered?






[TLOG-17] ExceptionInfo not printing data field when AOT? Created: 09/Aug/16  Updated: 09/Aug/16

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

Type: Enhancement Priority: Minor
Reporter: Andrea Richiardi Assignee: Alexander Taggart
Resolution: Unresolved Votes: 0
Labels: None


 Description   

The behavior of ExceptionInfo in presence of log4j2 and AOT is not very helpful, maybe because they changed the way it is printed out in this new version. In a repl I have the data field:

clojure.lang.ExceptionInfo: Oh noes! data: {:file "/tmp/boot.user8522818496965447008.clj", :line 71} clojure.lang.ExceptionInfo: Oh noes! data: {#object[clojure.lang.Keyword 0x1d2c6d6b ":what"] "happened"} clojure.core/ex-info/invokeStatic core.clj: 4617

But after the uberjar has been created (and AOT compiled), I get:

12:22:38.815 [main] ERROR mytest2.system - Uncaught exception on main clojure.lang.ExceptionInfo: Oh noes! at clojure.core$ex_info.invokeStatic(core.clj:4617) ~[mytest2-standalone.jar:?]

I can do some researching but I wanted to open an issue in case someone has something to pitch in. For example the Messages API has changed a bit.






[TLOG-18] Support custom levels Created: 27/Sep/16  Updated: 27/Sep/16

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

Type: Enhancement Priority: Minor
Reporter: Andrea Richiardi Assignee: Alexander Taggart
Resolution: Unresolved Votes: 0
Labels: None


 Description   

At the moment, if a custom log level is created, using for example Log4j2, an error is thrown.

However, custom levels are very powerful, especially given the wide set of appenders the Java logging ecosystem provides. A use case: I use tufte for profiling and I would really love to have a file with only the :profile level logged.






Generated at Sat Oct 01 13:57:50 CDT 2016 using JIRA 4.4#649-r158309.