Uploaded image for project: 'Maven SCM Publish Plugin'
  1. Maven SCM Publish Plugin
  2. MSCMPUB-13

automaticRemotePathCreation does not create parent directories

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

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 1.0
    • 3.1.0
    • None

    Description

      mvn scm-publish:publish-scm -Dscmpublish.pubScmUrl=scm:svn:.../${project.artifactId}/${project.version} fails if the directory ${project.artifactId} does not exist. This happens regardless of the automaticRemotePathCreation setting. Publishing the site of a new project therefore fails unless the SVN path is created manually.

      The root cause is that maven-scm-provider-svnexe does not add the "--parents" parameter to the svn mkdir command. I don't know if this should be considered a bug of the provider, or if the provider API should be enhanced to make this configurable.

      Attachments

        Issue Links

        Activity

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

          People

            michael-o Michael Osipov
            mikoch Michael Koch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment