Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
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
Attachments
Issue Links
- depends upon
-
SCM-748 Automatically create parent dirs with 'svn --parents'
- Closed
-
MSCMPUB-37 Upgrade to SCM 1.11.2
- Closed