[
http://www.stripesframework.org/jira/browse/STS-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11097#action_11097
]
Frederic Daoud commented on STS-414:
------------------------------------
Some comments on this:
- I agree that we should properly document the use of Log4J with SLF4J as this
is a common scenario.
- The issue with the line numbers, while a valid issue, is in my opinion a
separate issue than the switch from commons-logging to SLF4J. Indeed, the
problem with seeing line numbers from util.Log is because of the indirection,
not the use of SLF4J. I reproduced this problem with Stripes 1.4.3 and
commons-logging.
- We need to decide if we want to use SLF4J directly, or keep util.Log and find
a way to obtain the correct line numbers. Again, I think this is the subject of
a new JIRA issue.
Cheers,
Freddy
> update to commons logging 1.1.1
> -------------------------------
>
> Key: STS-414
> URL: http://www.stripesframework.org/jira/browse/STS-414
> Project: Stripes
> Issue Type: Improvement
> Reporter: Kai Grabfelder
> Assignee: 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://www.stripesframework.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 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
