Hello Garrett,
> It looks like the doTestDatedRevision stuff is still failing,
> as is setUp for AbstractRepositoryTest. Still can't manage
Could you please send me the console output generated by the tests? On my
linux box (running Gentoo) the main source of the problems was that file
timestamps are calcualted up to the seconds, not milliseconds, so comapring
files by timestamps only gave false positives. I've changed this code and
also got rid of File.rename(...) calls that doesn't work on Linux and all
the tests pass on my system now. If method setUp fails that actually means
that fixture repository was not created for some reason and it is no
surprise that all the tests will fail...
I do not have access to the MacOS, but of course would like to make javasvn
library work there as well, so, it will be very helpful if people will run
tests or, better, use the library :) in other then windows environments. To
run tests one have to:
1) check out sources from the repository
(http://80.188.80.120/svn/jsvn/trunk/)
2) modify javasvn-test/test.${OS}.properties file (test.mac.properties for
mac or test.unix.properties for unix)
3) run "ant test" in the root folder. Program will create ~/testRepo folder
where all test repositorires, working copies and log files will be created,
then it will start svnserve and apache2 on ports 3690 and 8080 by default.
Servers will be killed as soon as tests are finished.
4) collect console output and send the results to alex@tmate.org if there
are any problems.
Tests assumes that there are svn, svnserve and apache2 server a installed
and properties file defines their locations. On Linux I've used jdk 1.5.0,
svn 1.1.0 and apache 2.0.51 to run tests.
> to make the ra_dav tests work, but it's probably a local
> problem. I had to comment out a bunch of stuff in the
> httpd.conf template to get it to even start, so I probably
> removed something important.
This file is minimalistic configuration file for apache2 web server. It is
quite strange that you should comment anything in it to make apache work...
More details, like error messages will help to fix the problem.
> One other question... Is there any reason that your library
> deviates from the naming conventions used for the C version
> of Subversion. For example, you call working copies
> workspaces, which isn't exactly intuitive, considering that
> all the documentation about Subversion calls them working
> copies...
I will think about changing this name. However ISVNWorkspace interface
represents not a single working copy file but rather a whole checked out
project, that why I've named it "workspace". But may be ISVNWorkingCopy will
sound better. BTW, interface with similar capabilites in javahl library is
called SVNClientInterface.
> I also found the placing of the code to implement
> the two RA layers inside a package called 'io' not very
> intuitive, I/O is a rather nonspecific kind of name...
Here I have to disagree, I'm following the JDK naming in this case, where
the low-level IO classes are located in the java.(n)io package. In javasvn
library I'm using the same naming scheme, all the interfaces that abstracts
low-level communication are placed in the "org.tmatesoft.svn.core.io"
package, and their implementation (accordingly to eclipse guidelines) in the
"org.tmatesoft.svn.core.internal.io.svn" and
"org.tmatesoft.svn.core.internal.io.dav" packages.
> -----Original Message-----
> From: Garrett Rooney [mailto:rooneg@electricjellyfish.net]
> Sent: Wednesday, October 06, 2004 12:17 AM
> To: alex@tmate.org
> Cc: dev@subversion.tigris.org
> Subject: Re: Pure java subversion library
>
> Alexander Kitaev wrote:
> > Hello Garrett,
> >
> > All tests (svn,dav) for svn java library
> (http://tmate.org/svn/) pass
> > both on windows and linux, so I hope they will work on
> macOS as well,
> > so you may update library sources and give it a try.
>
> It looks like the doTestDatedRevision stuff is still failing,
> as is setUp for AbstractRepositoryTest. Still can't manage
> to make the ra_dav tests work, but it's probably a local
> problem. I had to comment out a bunch of stuff in the
> httpd.conf template to get it to even start, so I probably
> removed something important.
>
> Unfortunately I've exhausted my "play around with things"
> quota for today, so I don't know when I'll get back to this...
>
> One other question... Is there any reason that your library
> deviates from the naming conventions used for the C version
> of Subversion. For example, you call working copies
> workspaces, which isn't exactly intuitive, considering that
> all the documentation about Subversion calls them working
> copies... I also found the placing of the code to implement
> the two RA layers inside a package called 'io' not very
> intuitive, I/O is a rather nonspecific kind of name...
>
> -garrett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 7 14:18:30 2004