[Deploying Sakai] Replacing Log4j with Logback

Seth Theriault slt at columbia.edu
Wed May 29 22:11:23 PDT 2013

On Thu, May 30, 2013 at 12:49 AM, John Bush <john.bush at rsmart.com> wrote:
> Have you tried to use this migrator tool on all or part of the
> codecase yet?  It looks like there's a bunch of things it trips up on
> that have to be done manually, it would be helpful to know how
> widespread or not the manual work is.

I have tested it on parts of the codebase, and it works pretty much as

There will need to be manual inspection for sure since if you have
both JCL and JUL imports in the same file (yes, we have that!), you
get 2 sets of SLF4J import statements. In addition, the string
matching isn't always perfect:

Index: citations/citations-osid/web2bridge/src/java/edu/indiana/lib/osid/base/repository/http/Logger.java
--- citations/citations-osid/web2bridge/src/java/edu/indiana/lib/osid/base/repository/http/Logger.java
 (revision 125249)
+++ citations/citations-osid/web2bridge/src/java/edu/indiana/lib/osid/base/repository/http/Logger.java
 (working copy)
@@ -36,7 +36,7 @@

-        * Log a message
+        * Logger a message
        public void log(String entry)
        throws org.osid.repository.RepositoryException

Overall, I think it gives you a fast start on the tedium of the
migration, but in the end, you still have to double-check it.


More information about the production mailing list