lovely.
Tested and approved :-)
Thanks a lot!
2012/3/29 Alexander Kitaev :
>> Cool.
>> Any snapshots I can test here
>> http://maven.tmatesoft.com/content/repositories/snapshots/org/tmatesoft/svnkit/svnkit/
>> ?
>
> This new SVNStatus method is available in 1.7.4-rc3 build which we've
> published
> Cool.
> Any snapshots I can test here
> http://maven.tmatesoft.com/content/repositories/snapshots/org/tmatesoft/svnkit/svnkit/
> ?
This new SVNStatus method is available in 1.7.4-rc3 build which we've
published yesterday, there is a 1.7.4-rc3 bundle in the "releases"
repository which you may try
2012/3/28 Alexander Kitaev :
> Hello,
>
> I think the reason of the problem might be that for the working copy
> in the format (1.7) SVNKit reports now three-component SVNStatus
> objects, which consist of node, contents and properties statuses. In
> most cases new "node" status corresponds to the
Hello,
I think the reason of the problem might be that for the working copy
in the format (1.7) SVNKit reports now three-component SVNStatus
objects, which consist of node, contents and properties statuses. In
most cases new "node" status corresponds to the old "contents" one.
Today I have also a
Hello,
The cli says :
svn st
/Users/olamy/dev/sources/open-sources/maven-scm-provider-svnjava/target/scm-test/updating-copy/
A
/Users/olamy/dev/sources/open-sources/maven-scm-provider-svnjava/target/scm-test/updating-copy/src/test/java/org
A
/Users/olamy/dev/sources/open-sources/mav
