You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2018/09/09 08:11:00 UTC

[jira] [Reopened] (MSCMPUB-13) automaticRemotePathCreation does not create parent directories

     [ https://issues.apache.org/jira/browse/MSCMPUB-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hervé Boutemy reopened MSCMPUB-13:
----------------------------------

as seen in MSCMPUB-37, the commit didn't get to shared repository, then this issue is not fixed

[~michael-o] I hope you still have it locally then it's just a matter of pushing

> automaticRemotePathCreation does not create parent directories
> --------------------------------------------------------------
>
>                 Key: MSCMPUB-13
>                 URL: https://issues.apache.org/jira/browse/MSCMPUB-13
>             Project: Maven SCM Publish Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0
>            Reporter: Michael Koch
>            Assignee: Michael Osipov
>            Priority: Minor
>             Fix For: 3.1.0
>
>
> {{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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)