[ http://mc4j.org/jira/browse/STS-414?page=comments#action_10885 ] Remi VANKEISBELCK commented on STS-414: ---------------------------------------
Actually, you can already get rid of commons-logging very easily, as Logging classes are externalized in Stripes... Simply rewrite the Logger class, get it compiled as a .class in WEB-INF/classes and you're done ! As WEB-INF/classes is loaded before WEB-INF/lib, your impl will replace commons-logging's , and you can remove the jar. Another option is to overwrite commons logging's Log and LogFactory with the same technique. Ok, it's hackish and removing completely commons-logging eventually would be even better... but at least it allows to actually remove the guilty classloader confusing jar ;-P Cheers Remi > 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
