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

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org

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

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

Looks like the changes to the project specific URL properties are ignored ({{project.scm.*.connection}} and {{project.scm.*.developerConnection}}) as the value set via {{scm.url}} is the only one that is getting picked up, but it did override the connection URL from scm tag.

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