[jira] [Commented] (MRELEASE-1017) The option -Dproject.scm.developerConnection as specified in the guide does not work

["Hari Krishna Dara (JIRA)" <ji...@apache.org>]

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

Hari Krishna Dara commented on MRELEASE-1017:
---------------------------------------------

I also noticed that the values from release.properties don't take precedence. E.g., even though I changed {{developerConnection}} URL in release.properties, {{release:perform}} still used the value from the SCM tag. Documentation on {{release:perform}} doesn't indicate that overriding developerConnection this way should be possible, but there is documentation on other SCM properties (e.g., [connection|http://maven.apache.org/maven-release/maven-release-plugin/perform-mojo.html#connectionUrl]) that indicates that this should be possible.

> The option -Dproject.scm.developerConnection as specified in the guide does not work
> ------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-1017
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-1017
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.5.3
>            Reporter: George Belden
>            Priority: Major
>
> What I'm reporting is basically the same as the following which looks to never have been resolved.
> https://issues.apache.org/jira/browse/MRELEASE-707
>  
> The option -Dproject.scm.developerConnection as specified on the following guide does not work.
> [https://maven.apache.org/guides/mini/guide-releasing.html]
>  
> It would be nice if the documentation could be updated so as not to be misleading.  However it would be even nicer to have that functionality, as it is a critical configuration in order to be able to use this plugin in modern CI/CD pipelines.
> Is such a configuration planned for any future release?  I have already bolted this functionality onto the 2.5.3 source so that I can at least use this on my projects.  Otherwise this plugin is not usable for my team, hence why I am marking this as major.  But I do not understand the procedure for sharing this feature, or if it's already being added to a future release then it's a moot point.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)