[
https://issues.apache.org/jira/browse/SCM-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962053#comment-17962053
]
ASF GitHub Bot commented on SCM-558:
------------------------------------
jira-importer commented on issue #767:
URL: https://github.com/apache/maven-scm/issues/767#issuecomment-2964623109
**[Maria Odea B.
Ching](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=oching)**
commented
Hi Grant, for the other providers, the mkdir command is simply just add. But
for SVN provider, you can run mkdir in two ways:
* svn mkdir [DIRNAME]
* svn mkdir [REPO URL]
The related wagon-scm issue is for deploying documentation to a SCM
repository. The case there is when the specified path does not exist, the
deployment fails. So what we wanted to do was create the missing directory
paths first. In cases when the provider is SVN, we want to utilize the 'svn
mkdir [REPO URL]' command so that there's no need to checkout the entire source
tree just to create the directories. For the other SCM providers, I don't think
there's an equivalent for 'svn mkdir [REPO URL]' (only for 'svn mkdir
[DIRNAME]' to create/add dir in working copy has an equivalent) so what I did
with the CVS implementation for the mkdir command is to just invoke the the CVS
Add command from within. I'm still fixing some tests and I'll commit it later
if you want to take a look.
> Add support for 'mkdir' command
> -------------------------------
>
> Key: SCM-558
> URL: https://issues.apache.org/jira/browse/SCM-558
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: maven-scm-api
> Reporter: Maria Odea B. Ching
> Assignee: Maria Odea B. Ching
> Priority: Major
> Fix For: 1.5
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
