Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.1, 1.8
    • Fix Version/s: 1.9
    • Component/s: maven-scm-provider-svn
    • Labels:
      None
    • Environment:
      Windows xp, maven 2.0.9
    • Complexity:
      Intermediate
    • Number of attachments :
      1

      Description

      I have a need to use the SCM api to manipulate a local svn copy, but the svn provider can only work with remote copies.

      e.g. "svn info ." to get the reposirory URL etc from what Subversion has and not what you think it is.

      If you pass in a file:// URL it treats this as a repository and not a local copy - but if you don't use a url prefix and pass in just the path it fails to parse the URL in SvnScmProviderRepository.parseURL().

      The current workaround is to provide a custom SvnScmProviderRepository which overrides getURL to return the path which shows that the info command and others can work like this (however this obviously breaks anything that uses local file based repositories!)

        Issue Links

          Activity

          Hide
          James Nord added a comment -

          Digging through the code it seems like this should be supported and ends up in getRepositoryURL in SvnExeScmProvider.

          However this calls info which goes out and into AbstractCommand.execute(...) which does a check against the repo.

          I beleive this should call the info command directly.
          .

          Show
          James Nord added a comment - Digging through the code it seems like this should be supported and ends up in getRepositoryURL in SvnExeScmProvider. However this calls info which goes out and into AbstractCommand.execute(...) which does a check against the repo. I beleive this should call the info command directly. .
          Hide
          James Nord added a comment -

          fix for issue

          Show
          James Nord added a comment - fix for issue
          Hide
          Chris Graham added a comment -

          This patch still has not been applied. It is likely to be? Or, is the issue still relevant?

          Show
          Chris Graham added a comment - This patch still has not been applied. It is likely to be? Or, is the issue still relevant?
          Hide
          Robert Scholte added a comment -

          This seems to be the reason why the junit-tests for the maven-scm-publish-plugin fail under Windows.

          Show
          Robert Scholte added a comment - This seems to be the reason why the junit-tests for the maven-scm-publish-plugin fail under Windows.
          Show
          Robert Scholte added a comment - Fixed in https://git-wip-us.apache.org/repos/asf/maven-scm/commit/c96ca247 Thanks!

            People

            • Assignee:
              Robert Scholte
              Reporter:
              James Nord
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: