Thanks, Mark. That helped to make sure I was on the right track. I think
I've tracked down the problem, but I'm not sure exactly what the issue
is. SVNClientAdapter defines both ISVNStatus and ISVNInfo
/**
* An interface defining the status of one subversion item (file or
directory) in
* the working copy or repository.
*
* @author philip schatz
*/
public interface ISVNStatus {
...
}
/**
* Give information about one subversion item (file or directory) in the
* working copy
*/
public interface ISVNInfo {
...
}
However, this seems to be the opposite of what the command line client
defines:
maciek@maciek-desktop:~/svntest$ svn help status
status (stat, st): Print the status of working copy files and
directories.
...
maciek@maciek-desktop:~/svntest$ svn help info
info: Display information about a local or remote item.
...
However, at first glance, status and info do the right thing (maybe it's
just the javadoc that's incorect). I did notice that when I run svn info
on the command line, I get 'path' and 'name' properties, and, indeed,
the SvnTask class lists these as expected in the FILE_PROP_NAMES array.
Ah! I think I've just figured it out:
if (FILE_PROP_NAMES[0].equals(propName)) {
value = this.info.getFile();
if (value != null) {
value = ((File) value).getAbsolutePath();
}
} else if (FILE_PROP_NAMES[1].equals(propName)) {
value = this.info.getFile();
if (value != null) {
value = ((File) value).getName();
}
This code in Info.getValue (in svnant) assumes that the info is about a
local working copy file. We need to call a different set of methods in
getValue() to get information about a remote URL.
Also, I've noticed that there hasn't been repository activity in months.
Is development still active? Should I bother submitting a patch?
Thanks,
Maciek
On Fri, 2007-08-03 at 12:32 -0400, Mark Phippard wrote:
> On 8/3/07, Maciek Sakrejda <msakrejda@truviso.com> wrote:
> > No one? The odd thing is, I need svnjavahl.jar in my classpath, or the
> > task falls back to command line if I set
> >
> > javahl=false
> > svnkit=true
>
> I can help with that one. The JavaHL JAR is still needed by SVNKit.
> JavaHL includes several standard interfaces and classes that are used
> by SVNKit. JavaHL just includes one class that implements these
> interfaces and uses JNI calls to the SVN libraries. SVNKit just
> includes another implementation of that interface that uses pure Java.
>
> So the JavaHL JAR is a hard requirement even when using SVNKit.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Aug 3 22:46:33 2007