On Mon, Mar 8, 2010 at 10:51 AM, Hyrum K. Wright <[email protected]> wrote: > This means we now need to keep these constructors around for backward compat, > yes? > > (Even in cases where the constructor explicitly says something like "This > constructor should only > be called from JNI code."?)
These classes bleed into the ISVNClient interface so they are effectively public and ought to be usable by anyone providing an implementation of the interface. Another way to approach this would be to create additional interfaces for anything that is exposed directly or indirectly via ISVNClient and move all of our implementation classes into a package names "internal". Then we only need to version the interface methods and anyone that uses the internal implementation is on their own. -- Thanks Mark Phippard http://markphip.blogspot.com/
