[ http://mc4j.org/jira/browse/STS-414?page=comments#action_10908 ] 
            
Frederic Daoud commented on STS-414:
------------------------------------

Say, I just looked at the source code and Stripes is beautiful once again! 
Logging is wrapped in ONE SINGLE CLASS, net.sourceforge.stripes.util.Log. The 
dependence on commons-logging is hidden inside this class, and so shielded from 
the rest of the code. So, unless there's something that I'm missing here, 
switching to slf4j would mean just changing, in that one class, the 'realLog' 
instance variable to make it use slf4j instead of JCL. Then, commons-logging 
could disappear completely, and we wouldn't even jcl-over-slf4j, just slf4j 
pure.

What do you think?

Cheers,
Freddy

> update to commons logging 1.1.1
> -------------------------------
>
>                 Key: STS-414
>                 URL: http://mc4j.org/jira/browse/STS-414
>             Project: Stripes
>          Issue Type: Improvement
>            Reporter: Kai Grabfelder
>         Assigned To: Kai Grabfelder
>            Priority: Minor
>             Fix For: Release 1.5
>
>
> once commons logging 1.1.1 is release stripes should be updated to use it (in 
> order to resolve packaging issues for maven2 users)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://mc4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development

Reply via email to