Community
Participate
Working Groups
Currently when we use a cdo client with a protocol version, as defined by CDOProtocolConstants.PROTOCOL_VERSION, different of the one of server, the server throw a ProtocolVersionException which is catched by the net4j channel layer which dispatch a ChannelException to the client. The client can receive a ChannelException for different reasons, but to distinguish protocol version mismatch reason of other ones, he must parse the exception message. It would be more convenient to have ProtocolVersionException type accessible to client, for example by putting it in cdo.common or net4j.util plugin, and having this exception thrown to the client.
A first draft : https://git.eclipse.org/r/#/c/35598/ ChannelException should give more information about issue, in this case we need type of issue, protocol version mismatch, and the client and server protocol version to give feedback to end-user that it use an older or newer CDO client.
Moving all open bugzillas to 4.5.
Moving all unaddressed bugzillas to 4.6.
Moving all open bugs to 4.7
Moving all unresolved issues to version 4.8-
Moving all unresolved issues to version 4.9
Moving to 4.13.