[ http://mc4j.org/jira/browse/STS-414?page=comments#action_10913 ] Remi VANKEISBELCK commented on STS-414: ---------------------------------------
> Freddy was amazed : > 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 he he, that's exactly what my colleague at work told me last week ;-P And that's what I meant by overwriting the class : by rewriting this same class and dropping it into WEB-INF/classes, Stripes works without commons-logging in the classpath :-) The colleague has already coded a JMX / SysProps / Scripting management webapp with Stripes, and he doesn't have the commons-logging in it ! Slf4j simply solves the problem by allowing different packaging. But you would not have any issue if App Servers weren't including commons-logging in the root classpath ... > 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
