You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "George Belden (JIRA)" <ji...@apache.org> on 2018/11/03 17:03:00 UTC
[jira] [Updated] (MRELEASE-1017) The option
-Dproject.scm.developerConnection as specified in the guide does not work
[ https://issues.apache.org/jira/browse/MRELEASE-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
George Belden updated MRELEASE-1017:
------------------------------------
Priority: Blocker (was: Minor)
> 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: Blocker
>
> 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. 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)