> 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.

Alexander Kitaev,
TMate Software,
http://subgit.com/ - Svn to Git Migration!
http://svnkit.com/ - Java [Sub]Versioning Library!
http://hg4j.com/ - Java Mercurial Library!
http://sqljet.com/ - Java SQLite Library!



On 29 March 2012 12:09, Olivier Lamy <[email protected]> wrote:
> 2012/3/28 Alexander Kitaev <[email protected]>:
>> 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 added a method getCombinedNodeAndContentsStatus() to
>> the SVNStatus object, which you may use to get status value same as
>> that displayed by the command line client.
> Cool.
> Any snapshots I can test here
> http://maven.tmatesoft.com/content/repositories/snapshots/org/tmatesoft/svnkit/svnkit/
> ?
> Thanks
>>
>> Alexander Kitaev,
>> TMate Software,
>> http://subgit.com/ - Svn to Git Migration!
>> http://svnkit.com/ - Java [Sub]Versioning Library!
>> http://hg4j.com/ - Java Mercurial Library!
>> http://sqljet.com/ - Java SQLite Library!
>>
>>
>>
>> On 28 March 2012 18:31, Olivier Lamy <[email protected]> wrote:
>>> 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/maven-scm-provider-svnjava/target/scm-test/updating-copy/src/main/java/org
>>> A       
>>> /Users/olamy/dev/sources/open-sources/maven-scm-provider-svnjava/target/scm-test/updating-copy/src/main/java/org/Foo.java
>>> M       
>>> /Users/olamy/dev/sources/open-sources/maven-scm-provider-svnjava/target/scm-test/updating-copy/pom.xml
>>>
>>> whereas the status is modified in svnkit.
>>> Is there any know issues ?
>>> To reproduce have a look at this project:
>>> http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/
>>>
>>> svn co 
>>> http://svn.codespot.com/a/apache-extras.org/maven-scm-provider-svnjava/trunk/
>>> maven-scm-provider-svnjava
>>> mvn clean install
>>>
>>> The current failure is due to this non correct status
>>> Any ideas ?
>>>
>>> Thanks!
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>

Reply via email to