Hello,
For the SVNKit version v1.3.3; SVN version v1.6.11
A for the "fullProjectPath", it is an absolute path.
I dont know the working copy status, is there a way / function for getting
the working copy status in SVNKit?
May I know the reason why I get this EmptyStackException?

Thank You for your help. :-)


Dmitry Pavlenko-2 wrote:
> 
> Hello,
> could you please provide more information:
> What SVNKit version do you use?
> Is "fullProjectPath" an absolute or relative path?
> What is your working copy status (please provide "svn status -v" output or
> describe it somehow)?
> 
>> I've been getting this error
>> 
>> java.util.EmptyStackException
>>      at java.util.Stack.peek(Stack.java:85)
>>      at
>> org.tmatesoft.svn.core.internal.io.fs.FSCommitEditor.addDir(FSCommitEditor.
>> java:149) at
>> org.tmatesoft.svn.core.internal.wc.SVNCommitter.handleCommitPath(SVNCommitt
>> er.java:132) at
>> org.tmatesoft.svn.core.internal.wc.SVNCommitUtil.driveCommitEditor(SVNCommi
>> tUtil.java:92) at
>> org.tmatesoft.svn.core.internal.wc.SVNCommitter.commit(SVNCommitter.java:36
>> 6) at
>> org.tmatesoft.svn.core.wc.SVNCommitClient.doCommit(SVNCommitClient.java:100
>> 9) at
>> org.tmatesoft.svn.core.wc.SVNCommitClient.doCommit(SVNCommitClient.java:896
>> ) at
>> org.tmatesoft.svn.core.wc.SVNCommitClient.doCommit(SVNCommitClient.java:828
>> ) at com.ctrlspace.vcs.SVNKitWrapper.doCommit(SVNKitWrapper.java:147) at
>> com.ctrlspace.vcs.commands.PushCommand.doPush(PushCommand.java:130)
>> 
>> when using
>> 
>> SVNCommitInfo info = manager.getCommitClient().doCommit(
>>                              new File[] { new File(fullProjectPath) }, 
>> false, commitMessage,
>>                              null, null, true, false, SVNDepth.INFINITY);
>> 
>> Note:
>> new File[] { new File(fullProjectPath)  -> it is the list of files that
>> the
>> user want to create
> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/EmptyStackException-when-using-doCommit%28%29-tp34122126p34126667.html
Sent from the SVNKit - Users mailing list archive at Nabble.com.


Reply via email to