commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Rosenvold <>
Subject [io] How picky about backward compatibility ?
Date Sat, 20 Jun 2015 05:48:13 GMT
I reverted the fix in simply because
it broke backward compatibility in a subtle way. The BrokenNNStream classes
supply the same instance of the IOException on all methods (and there are
tests that assert it)

Given some of the discussions I've seen about backward compatibility here,
I felt it best to revert (even though API-wise I feel this change is within
reasonable even for a minor release). WDYT ?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message