DO NOT REPLY [Bug 40667] Change protected Loggers to private

2012-04-01 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=40667

Glenn Adams gl...@skynav.com changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--- Comment #7 from Glenn Adams gl...@skynav.com 2012-04-01 06:39:29 UTC ---
batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.


DO NOT REPLY [Bug 40667] - Change protected Loggers to private

2006-10-05 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40667.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40667


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED




--- Additional Comments From [EMAIL PROTECTED]  2006-10-05 11:46 ---
Patch extended to all LMs which use a logger and applied. Andrejus, thanks for
your patch.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


DO NOT REPLY [Bug 40667] - Change protected Loggers to private

2006-10-04 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40667.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40667





--- Additional Comments From [EMAIL PROTECTED]  2006-10-04 12:15 ---
Andrejus,

Thanks for your patch. I have a few comments.

1. Your patch for src/java/org/apache/fop/layoutmgr/PageBreakingAlgorithm.java
reads:

 /** the logger for the class */
 protected static Log classLog = 
LogFactory.getLog(PageBreakingAlgorithm.class);
 
+/** the logger for the instance */
+private static Log log = classLog;

Why don't you remove 'protected static Log classLog'?

Re the comment, a static variable is for the class, not for the instance.

2. In the LayoutManagers, there is a protected static Log instance in
org.apache.fop.layoutmgr.AbstractBaseLayoutManager, assigned to class 
LayoutManager:

protected static Log log = LogFactory.getLog(LayoutManager.class)

This is used by all LayoutManagers. I can imagine that you find this too coarse,
and prefer to see a different logger for each LayoutManager, but then it would
be better to do so for each LayoutManager.

Regards, Simon


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


DO NOT REPLY [Bug 40667] - Change protected Loggers to private

2006-10-04 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40667.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40667





--- Additional Comments From [EMAIL PROTECTED]  2006-10-04 12:24 ---
Hi Simon,

I prefer to touch others code in very kind matter, meaning that I'd like to 
see as small recompiling as possible (in this case I wanted to touch just log 
members and not classLog I had no knowledge about). Yes, there is next step to 
do to change all other protected Loggers for LMs, but for me it would be much 
easier to to if we would deal with code tagging/modules/SVN branches instead 
of direct text patches. Right now I've applied Patrick's patch and to change 
other Loggers to private as well I would need once again to checkout whole 
source tree to another project and make those changes there. Actually I've 
planned finish that after I'll get some understanding of Patrick's code as 
well as with LMs invocations.

Sorry if it seems incomplete for you right now, but I've tried to make code 
after changes to be compilable.

Andrejus

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


DO NOT REPLY [Bug 40667] - Change protected Loggers to private

2006-10-04 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40667.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40667





--- Additional Comments From [EMAIL PROTECTED]  2006-10-04 12:33 ---
(In reply to comment #3)

 members and not classLog I had no knowledge about). Yes, there is next step 
 to 
 do to change all other protected Loggers for LMs, but for me it would be much 
 easier to to if we would deal with code tagging/modules/SVN branches instead 
 of direct text patches. Right now I've applied Patrick's patch and to change 

Indeed, doing this by patches is bothersome. But as it is, the patch is a bit
small and random. I would prefer it if you would make the required changes in
your working copy and submit them in a patch which contains more work.

Of course, I could make the changes to the LM tree myself. What do the FOP
committers think: Give each LM its own logger? It will provide more clarity
during debugging, but it will also increase the number of loggers considerably.

Simon


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


DO NOT REPLY [Bug 40667] - Change protected Loggers to private

2006-10-04 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40667.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40667





--- Additional Comments From [EMAIL PROTECTED]  2006-10-04 14:13 ---
(In reply to comment #4)
 Of course, I could make the changes to the LM tree myself. What do the FOP
 committers think: Give each LM its own logger? It will provide more clarity
 during debugging, but it will also increase the number of loggers 
 considerably.

+1 from me. It bugs me every now and then but so far I've never had enough
energy to actually do something about it. I only changed something for the
breaking algorithm where it was essential for me to keep line break stuff apart
from page break stuff while debugging.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


DO NOT REPLY [Bug 40667] - Change protected Loggers to private

2006-10-03 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=40667.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40667





--- Additional Comments From [EMAIL PROTECTED]  2006-10-03 07:03 ---
Created an attachment (id=18956)
 -- (http://issues.apache.org/bugzilla/attachment.cgi?id=18956action=view)
Corrects Logger in several LM classes

Corrects (adds where missed) Logger from protected to private in these classes:

LineLayoutManager, TableCellLayoutManager, TableLayoutManager,
BreakingAlgorithm, PageBreakingAlgorithm

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.