WebDAV publish of a folder fails with binaryDiff=true on 2.0.0-rc1 and beta5

[GoogleCodeExporter]

The IOException contains strangely "LATEST" in the path.
Publish works with ivy-svn 1.4.

settings:
<svn name="svn_ivy" repositoryRoot="${svn.server.url}/repopath"
userName="${svn.username}" userPassword="${svn.password}" >
  <ivy pattern="[organisation]/[module]/[revision]/ivy.xml" />
  <artifact
pattern="[organisation]/[module]/[revision]/[type]/[artifact].[ext]" />
</svn>

log:
:: publishing :: org.my#module
Scheduling publish to
http://svn.repo.host/repopath/org.my/module/1.2.3/classes/module.jar
Scheduling publish to
http://svn.repo.host/repopath/org.my/module/1.2.3/classes/module.jar.sha1
Scheduling publish to
http://svn.repo.host/repopath/org.my/module/1.2.3/classes/module.jar.md5
    published module to org.my/module/1.2.3/classes/module.jar
Scheduling publish to
http://svn.repo.host/repopath/org.my/module/1.2.3/sources/module.zip
Scheduling publish to
http://svn.repo.host/repopath/org.my/module/1.2.3/sources/module.zip.sha1
Scheduling publish to
http://svn.repo.host/repopath/org.my/module/1.2.3/sources/module.zip.md5
    published module to org.my/module/1.2.3/sources/module.zip
Scheduling publish to
http://svn.repo.host/repopath/org.my/module/1.2.3/javadocs/module.zip
Scheduling publish to
http://svn.repo.host/repopath/org.my/module/1.2.3/javadocs/module.zip.sha1
Scheduling publish to
http://svn.repo.host/repopath/org.my/module/1.2.3/javadocs/module.zip.md5
    published module to org.my/module/1.2.3/javadocs/module.zip
Scheduling publish to http://svn.repo.host/repopath/org.my/module/1.2.3/ivy.xml
Scheduling publish to
http://svn.repo.host/repopath/org.my/module/1.2.3/ivy.xml.sha1
Scheduling publish to
http://svn.repo.host/repopath/org.my/module/1.2.3/ivy.xml.md5
    published ivy to org.my/module/1.2.3/ivy.xml
Commit finished r1269 by 'svn.username' at Thu Nov 13 12:52:42 EET 2008
Copying from org.my/module/LATEST/javadocs to org.my/module/1.2.3/javadocs
Aborting transaction

exception:
java.io.IOException
    at
fm.last.ivy.plugins.svnresolver.SvnRepository.commitPublishTransaction(SvnReposi
tory.java:208)
    at
fm.last.ivy.plugins.svnresolver.SvnResolver.commitPublishTransaction(SvnResolver
.java:58)
...
Caused by: org.tmatesoft.svn.core.SVNException: svn: File not found:
transaction '1269-zc', path '/org.my/module/1.2.3/1.2.3/javadocs'
svn: '/repopath/!svn/bc/1269/org.my/module/LATEST/javadocs' path not found:
404 Not Found (http://svn.repo.host>)
    at
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64
)
    at
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51
)
    at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doCopy(DAVConnection.java:4
12)
    at
org.tmatesoft.svn.core.internal.io.dav.DAVCommitEditor.addDir(DAVCommitEditor.ja
va:154)
    at
fm.last.ivy.plugins.svnresolver.SvnPublishTransaction.copyDiff(SvnPublishTransac
tion.java:338)
    at
fm.last.ivy.plugins.svnresolver.SvnPublishTransaction.commit(SvnPublishTransacti
on.java:174)
    at
fm.last.ivy.plugins.svnresolver.SvnRepository.commitPublishTransaction(SvnReposi
tory.java:206)
    ... 20 more

Original issue reported on code.google.com by jkyto...@gmail.com on 13 Nov 2008 at 11:18

[GoogleCodeExporter]

Ah, that LATEST was of course the folder need by tge new binaryDiff feature.
Disabling binaryDiff fixed the problem. So only publish with binaryDiff is 
broken in
my environment.

Original comment by jkyto...@gmail.com on 13 Nov 2008 at 11:44

[GoogleCodeExporter]

Original comment by massdosage on 26 Nov 2008 at 4:51

• Changed title: WebDAV publish of a folder fails with binaryDiff=true on 2.0.0-rc1 and beta5

[GoogleCodeExporter]

Can you please also post the snippet of your ivy.xml which specifies the 
artifacts
you are trying to publish? And a short description of what exactly your publish
operation contains. I'm most interested in where that "javadocs" folder is 
coming from.

We've only ever published files (.jar, .war, .tgz etc.) so haven't run into this
issue. This looks like it only occurs if you publish a folder, which I wasn't 
aware
one could do. Let me know and I can then look into creating a unit test to 
reproduce
this and will then take it from there.

Original comment by massdosage on 26 Nov 2008 at 5:12

[GoogleCodeExporter]

No reaction on this issue and nobody else has reported it, so closing.

Original comment by massdosage on 8 Apr 2010 at 2:42

• Changed state: Invalid