Clirr reports several instances where the backward compatibility with 4.0-beta1 has been broken.

We basically have two options
(1) revert the changes
(2) document the breakage in the release notes, communicate that to the Android folks, and try to convince them that was worthwhile, as most of the changes are very subtle and are intended to ensure thread safety of affected classes.

Bob,

What is your take? Would you (that is Google) be able to live with that?

Oleg


[INFO] [clirr:check]
[INFO] Comparing to version: 4.0-beta1
[ERROR] org.apache.http.conn.BasicEofSensorWatcher: Field attemptReuse is now final [ERROR] org.apache.http.conn.BasicEofSensorWatcher: Field managedConn is now final [ERROR] org.apache.http.impl.client.RoutedRequest: Accessibility of field request has been weakened from protected to private [ERROR] org.apache.http.impl.client.RoutedRequest: Accessibility of field route has been weakened from protected to private [ERROR] org.apache.http.impl.conn.DefaultClientConnectionOperator: Field schemeRegistry is now final [ERROR] org.apache.http.impl.conn.DefaultHttpRoutePlanner: Field schemeRegistry is now final [ERROR] org.apache.http.impl.conn.ProxySelectorRoutePlanner: Field schemeRegistry is now final [ERROR] org.apache.http.impl.conn.SingleClientConnManager: Field alwaysShutDown is now final [ERROR] org.apache.http.impl.conn.SingleClientConnManager: Field connOperator is now final [ERROR] org.apache.http.impl.conn.SingleClientConnManager: Field schemeRegistry is now final [ERROR] org.apache.http.impl.conn.tsccm.ConnPoolByRoute: Removed field maxTotalConnections [ERROR] org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager: Field connOperator is now final [ERROR] org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager: Field schemeRegistry is now final [ERROR] org.apache.http.impl.cookie.BrowserCompatSpec: Accessibility of field DATE_PATTERNS has been weakened from protected to private

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to