You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Tran (JIRA)" <ji...@codehaus.org> on 2014/05/06 20:54:11 UTC

[jira] (SCM-741) scm:validate for svn should offer a way to check the current directory actually matches what's declared in the pom

     [ https://jira.codehaus.org/browse/SCM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Tran reopened SCM-741:
--------------------------


Need to reopen this issue to track the failing IT introduced by this fix

http://maven.40175.n5.nabble.com/FYI-maven-scm-plugin-IT-is-failing-since-Feb-25-td5792659.html

> 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)