McClain Looney wrote:
> On Dec 10, 2003, at 6:31 PM, Geoff Howard wrote:
>
>> I tried recently and again last night with the eclipse 3 branch but
>> was having a lot of problems getting the project recognized. I read
>> the paper by Sunghun Kim & Guozheng Ge posted here recently but it
>> seemed to be missing important details about the subclipse3 branch.
>
> after checking it out, you should reocompute the project classpaths.
> eclipse will correct everything by inserting the right libs for your
> platform.
Excellent - that was just the trick. For the record, I checked out
core, core-windows, ui with the M4 build using m4. shutdown, deleted
the .metadata dir, started back up in M5 and imported the projects.
open the plugin perspective, right click on plugin.xml (core first, then
ui) "Compute Classpath...", and bingo - it builds
copy libdb40.dll, libeay32.dll, svnjavahl.dll and ssleay32.dll to the M5
eclipse root and start the runtime workbench, and I'm able to open the
svn perspective and create a new repository location.
Except...
this still has the same behavior with https urls. I still get:
org.tigris.subversion.javahl.ClientException:
Bad URL passed to RA layer
svn: Unrecognized URL scheme: "https:....."
So it seems that svnjavahl.dll is still not built with ssl support?
For kicks I copied over all the dlls from tortoise svn instead of the
ones from core-windows and still got the same error, though I'm happily
connecting to an https repository with that tortoise install so maybe
that's not it.
Help would be greatly appreciated.
Geoff
Received on Thu Dec 11 15:33:45 2003