Steven is absolutely correct when he says "You haven't done a good enough job promoting it" ("it" being Logger). Despite my best efforts, promoting Logger is something I've struggled with and need some help.

Based on past emails and conversations, I know they're a lot of developers and organizations using Logger. If you're using Logger, either personally or within your organization, I need your help. Please blog about it (and post the link in the comments section below), email me a quote that I can use (martin@clarifit.com), Tweet about it (use #orcllogger), or mention it at the next conference you go to.

I used to maintain a LOGGER project of my own (yes, same name and even quite similar approach) until I came across yours some months ago. Now I'm (re-)writing the PL/SQL Code Generator that I created for my LOGGER package so that it fits for yours, too.

With this APEX application, PL/SQL code can be easily upgraded to embrace the LOGGER interface. Instrumenting existing code is a matter of a few seconds per copy/paste. Another feature is the PLSQLdoc style documentation of new or existing routines.