DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27231>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27231 [collections] Change to HashEntry inner class of AbstractHashedMap [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Change to HashEntry inner |[collections] Change to |class of AbstractHashedMap |HashEntry inner class of | |AbstractHashedMap ------- Additional Comments From [EMAIL PROTECTED] 2004-02-25 18:09 ------- Added [collections] to bug summary. Does changing HashEntry from a protected static inner class to a public inner interface break binary compatibility? Perhaps if you were to introduce an inner interface called something other than HashEntry and have the existing HashEntry class implement it, that would work. see > http://www.eclipse.org/eclipse/development/java-api-evolution.html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
