You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Fabian Christ (JIRA)" <ji...@apache.org> on 2013/03/20 09:33:16 UTC

[jira] [Commented] (STANBOL-989) Wrong scm information in enhancement-engines modules

    [ https://issues.apache.org/jira/browse/STANBOL-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607395#comment-13607395 ] 

Fabian Christ commented on STANBOL-989:
---------------------------------------

Yes, that happened because I merged the updated POMs from the release branch after the release back to the trunk and did forget about the SCM paths. Sorry for that. One more thing to think about in the release process...
                
> Wrong scm information in enhancement-engines modules
> ----------------------------------------------------
>
>                 Key: STANBOL-989
>                 URL: https://issues.apache.org/jira/browse/STANBOL-989
>             Project: Stanbol
>          Issue Type: Bug
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>            Priority: Trivial
>
> All enhancement-engines modules that where released in enhancement-engines-0.10.0 do have wrong <connection> and <developerConnection> information as
>     scm:svn:http(s)://svn.apache.org/repos/asf/stanbol/branches/STANBOL-913/{module-path}
> is stated instead of 
>     scm:svn:http(s)://svn.apache.org/repos/asf/stanbol/trunk/enhancement-engines/{module-path}
> As STANBOL-913 was the issue for the enhancement-engines-0.10.0 and the wrong URL points to the release branch the assumption is that this happened as part of the release process.
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira