JavaHL: Serializable and breaking binary compatibility?

I needed to serialize a Revision and discovered that the class doesn't
implement java.io.Serializable.

I have a patch ready that serialized this class and any other class that
doesn't include native methods and just acts like a C structure for data.

ChangePath
CommitItem
CopySource
DirEntry
Info
Info2
Lock
MergeInfo
ProgressEvent
Revision
RevisionRange
Status

Will this break Java code that compiled against the old,
non-serializable classes?

If it does, then I propose we have 1.5 be a binary API incompatible
release and do the following:

1) Make anything serializable that could be.
2) Introduce the microseconds time that apr_time_t holds throughout the
API, or at least add the fields to carry the data.

We won't be changing the API from a source point of view, so any clients
could just do quick recompile against JavaHL 1.5 and be up and running.
  I do need the microseconds time for my project also.

Thoughts?

I would like to do this before 1.5 branches.

Regards,
Blair

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 23 23:10:03 2007