Publishes with ROOT repository location ommitted.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create an SVN repository with https access
2. Schedule a publish using a resolve as follows: 

       <svn name="ivysvn"
             checkmodified="true"
             repositoryRoot="https://vcs.orgname.com/svn/repos/PMBU/ivyrepo/"
             userName="${svn.user.name}"
             userPassword="${svn.user.password}"
             keyFile="${ssh.keyfile}"
             sshPort="${ssh.port}"
             sshPassphrase="${ssh.keyfile.passphrase}"
             certFile="${ssl.certfile}"
             storageAllowed="${svn.storage.allowed}"
             binaryDiff="${svn.binarydiff}"
binaryDiffFolderName="${svn.binarydiff.folder}"
             retrieveRevision="${svn.retrieve.revision}"
             cleanupPublishFolder="${svn.cleanup.publish.folder}">
            <ivy pattern="/[organisation]/[module]/[revision]/ivy.xml"/>
            <artifact
pattern="/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"/>
        </svn>

What is the expected output? What do you see instead?

Expected a commit message that concludes with: 

    published ivy to
https://vcs.orgname.com/svn/repos/PMBU/ivyrepo/orgname/pm-common/666/ivy.xml

Actual outcome: 

The repository root is missing. The module is published to: 

https://vcs.orgname.com/svn/repos/orgname/pm-common/666 when it should have
been published to: 

https://vcs.orgname.com/svn/repos/PMBU/ivyrepo//orgname/pm-common/666/

What version of the product are you using? On what operating system?

Using Ivy 2.1.0 (also tried 2.0.0)
IvySvn 2.0.0

Please provide any additional information below.

Perhaps it's because our Ivy repository is set up to be a sub-folder of
another larger repository? 

Original issue reported on code.google.com by jasper.r...@gmail.com on 22 Feb 2010 at 10:04

[GoogleCodeExporter]

This should be fixed in IvySvn 2.1.0 which I hope to release in a week or two. 
The
2.0.0 version assumed that repositoryRoot was the root of the entire SVN 
repository,
not a sub-folder. You can either wait for 2.1.0 or try a trunk build. If you're 
going
to try the latter let me know as you'll need to make some config changes which 
I have
yet to add to the wiki as part of the upgrade procedure from 2.0.0 to 2.1.0.

Original comment by massdosage on 8 Apr 2010 at 3:00

• Changed state: Fixed