Re: [Exist-development] Subversion extension breaking build in trunk?

[Joe W. <jo...@gm...>]

Hi Dmitriy,

FYI, the build process on trunk still fails whenever the build
properties are set to include.feature.svn = true, unless I copy the
old svnkit jars into lib/user.  I'm concerned that new users who try
to use 2.0RC or 2.0-final will be frustrated when they try to enable
the SVN feature.  Do you have an idea for how to solve this?  I
proposed some ideas below.

Thanks for your ideas,
Joe

On Sat, Jul 7, 2012 at 3:10 PM, Joe Wicentowski <jo...@gm...> wrote:
> Hi Dmitriy,
>
>>>> use older version of svn jar
>>>
>>> DO you mean Joe needs to use an older version of a jar? is it the svnkit jar files?
>>
>> yes
>
> I see: the SVN extension skips downloading the svnkit jars if they're
> already present, but if they're missing, it downloads version 1.3.3
> (see extensions/svn/build.xml line 75).  Since I had already run
> "build.sh svn-download", the jars were present, but this
> "svn-download" step actually downloaded version 1.3.7
> (build/scripts/subversion.xml line 29).
>
> Given this, I thought the solution was to change
> build/scripts/subversion.xml to reference version 1.3.3, but when I do
> this, "build svn-download" fails, since this version isn't available
> at the location where the script looks:
> http://maven.tmatesoft.com/content/repositories/releases/org/tmatesoft/svnkit/svnkit-cli/1.3.3/svnkit-cli-1.3.3.jar.
>  So I think our options for fixing the build are either:
>
> 1. Find 1.3.3 and update the download URLs in
> build/scripts/subversion.xml to point to that instead of 1.3.7.
>
> - or -
>
> 2. Fix the SVN extension's apparent incompatibility with 1.3.7.
>
> If there's anything I can do to help, let me know.
>
> Thanks,
> Joe