https://bz.apache.org/bugzilla/show_bug.cgi?id=59791
--- Comment #8 from Javen O'Neal <[email protected]> --- Should we add some kind of warning or decoration to methods that will change their return value so that users can get a heads up before the signature changes? @deprecation implies the method is going away, but has warnings that integrate well with IDEs and the project can be built to treat deprecation warnings Searching for all public methods using CellType setters: $ grep -nr --exclude-dir=".svn" -P "public [^\(]+\([^\)]*CellType [^\)]+\)" src getters: $ grep -nr --exclude-dir=".svn" -P "public [^\(]*CellType [^[(]*\([^\)]*\)" src With r1751273, I believe I have reverted all public constructors and methods to be backwards compatible (at the binary level). There were some protected methods or inner classes that seemed unlikely to be used in projects where changing the return type would be a concern. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
