DO NOT REPLY [Bug 35654] New: - binary incompatibility between 1.2.xx Filter and 1.3 Filter

[bu...@apache.org]

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=35654>.
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=35654

           Summary: binary incompatibility between 1.2.xx Filter and 1.3
                    Filter
           Product: Log4j
           Version: 1.2
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P2
         Component: Other
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: hoju@visi.com


In Log4j-1.2.xx, the "next" variable in org.apache.log4j.spi.Filter is public. 
This was made private in Log4j-1.3 and added getter/setter for access instead. 
This is the right way to go, however for projects such as LogWeb which use the
Log4j API extensively, this creates an incompatibility between 1.2.xx and 1.3.

I propose one of two solutions...

1.  make "next" public again in 1.3 (yuck!)

2.  release a version of 1.2.xx with getter/setters just as the 1.3 has.  1.2.12
would be a great candidate!  "next" would be left public in 1.2.xx with a
deprecation warning to use the getter/setter methods.  LogWeb and other like
code can move to support 1.2.12+ and use the getter/setter methods to be
compatible with 1.3


Jake

-- 
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.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org