Uploaded image for project: 'Maven Wagon'
  1. Maven Wagon
  2. WAGON-42

wagon-scm (svn provider) - large paths under windows breaks download.

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Won't Fix
    • 1.0-alpha-6
    • None
    • wagon-scm
    • None

    Description

      I have a deep path in windows, plus a repository housed in svn.

      When performing a 'mvn compile', it fails with not finding the artifact.

      Using mvn --debug shows no error message from wagon-scm (svn).

      If I go into the target/checkout/.... directory, i see an empty directory with the '.svn' working directory.
      performing a 'svn update .' in that directory reveals the reason ...

      jerdfelt@EXSISTO /c/code/mergere/amex/AXP-EntBuildEnv/tools/branches/mergere-discovery-wizard/mergere-discovery-core/target/checkout/org/apache/maven/repository/maven-repository-indexer/1.0-SNAPSHOT
      $ svn update .
      svn: Can't open file '.svn/text-base/maven-repository-indexer-1.0-20060418.201022-1.jar.md5.svn-base': File name too long

      I think a general "if windows, and path exceeds maximum, throw error before attempting process' kind of functionality needs to exist.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            brett Brett Porter
            joakime Joakim Erdfelt
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 5.5h
                5.5h

                Slack

                  Issue deployment