[
https://jira.codehaus.org/browse/SCM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342142#comment-342142
]
Baptiste Mathus commented on SCM-741:
-------------------------------------
For the record:
(the complete syntax) :
mvn org.apache.maven.plugins:maven-scm-plugin:1.10-SNAPSHOT:validate
-DscmCheckWorkingDirectoryUrl=true
will now do the job (double-check you have the last snapshot locally, if not
this won't do anything).
Note that the 1.10 hasn't been released yet.
> scm:validate for svn should offer a way to check the current directory
> actually matches what's declared in the pom
> ------------------------------------------------------------------------------------------------------------------
>
> Key: SCM-741
> URL: https://jira.codehaus.org/browse/SCM-741
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-svn
> Reporter: Baptiste Mathus
> Fix For: 1.10
>
>
> scm:validate for svn currently only validates the URL has a good format, but
> nothing about its actual validity.
> The first thing that could be done is to offer a way use the svn info output,
> retrieve the "URL:" line and check if it matches the
> project/scm/developerConnection declaration (or one of them?).
> This would be useful to the release-plugin. A lot of people already got
> burned by the svn copy that would actually copy something else that the
> current project content to the tag because the URL was wrong (see
> MRELEASE-512 and MRELEASE-494 and MRELEASE-445 for just some examples).
> Currently working on a patch for it. But if you have any feedback, I'd be
> glad to hear about it.
> Cheers and thanks for the work guys.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
