[
https://issues.apache.org/jira/browse/SCM-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961969#comment-17961969
]
ASF GitHub Bot commented on SCM-511:
------------------------------------
jira-importer closed issue #725: [SCM-511] Build error when publishing a new
version of the site through the command line. Error: Embedded error: Unable to
commit file. The svn command failed. svn: URL '----------' doesn't exist
URL: https://github.com/apache/maven-scm/issues/725
> Build error when publishing a new version of the site through the command
> line. Error: Embedded error: Unable to commit file. The svn command failed.
> svn: URL '----------' doesn't exist
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SCM-511
> URL: https://issues.apache.org/jira/browse/SCM-511
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-site
> Environment: Command line, Java
> Reporter: Rolan Sanchez
> Priority: Minor
>
> In declaring interdependencies by referencing project properties e.g.,
> reports/${project.groupId}/${project.artifactId}/${project.version}
> if a newer version of the site is created and then if try to publish it to
> SVN, Maven cannot create the parent directory.
> Since the parent directory does not exist in SVN, Maven does not
> automatically create and publish site to SVN and an error is thrown:
> " Embedded error: Unable to commit file. The svn command failed. svn: URL
> 'https://......../svn/....../trunk/www/......../com.............ears/..................../1.0.2-SNAPSHOT/.............'
> doesn't exist".
> Maven expects at least parent directory to be created manually in order to
> publish the site before the build.
> Instead the Directory creation for the newer version should be automatic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
