You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Hyrum K. Wright" <hy...@mail.utexas.edu> on 2010/02/10 02:35:19 UTC
Re: JavaHL package name? (was: Discussion: graduating Subversion)
On Jan 27, 2010, at 2:18 PM, Hyrum K. Wright wrote:
>
> On Jan 26, 2010, at 2:08 PM, Martin Furter wrote:
>
>>
>>
>> On Mon, 25 Jan 2010, Justin Erenkrantz wrote:
>>
>>> My take is deprecate the old package names (org.tigris.*), add the new
>>> package name (org.apache.subversion.*), and remove the deprecated
>>> names whenever we go to 2.0.
>>>
>>> I'm moderately ambivalent on whether this happens for 1.7 or if can
>>> wait for 1.8...
>>>
>>> I don't see much else we can do under our versioning policies. -- justin
>>
>> How about transforming all classes in org.tigris.subversion to wrappers around org.apache.subversion classes and replace the interfaces with empty ones derived from the apache interfaces (plus their current parent interface)?
>
> I think this is the way to go. I was playing around last night with re-jiggering the java code into the new package(s), and got something reasonable put together. I'll commit it shortly, and I invite folks to comment / criticize.
Alrighty. As of r908323, I've got the JavaHL packages moved over to the Apache namespace, with the old package implemented as a wrapper around the new. I have had to make a number of changes to the JavaHL build system, and have probably completely broken the JavaHL build system on Windows, so I encourage somebody building JavaHL on Windows to take a look.
Validation of the new classes and the wrappers would be nice, too.
Thanks,
-Hyrum