[jira] [Closed] (MRELEASE-983) Documentation for release plugin has still not been corrected.

["Robert Scholte (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MRELEASE-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MRELEASE-983.
-----------------------------------
      Assignee: Robert Scholte
    Resolution: Invalid

If you take a closer look at the scm goals, you're see:
{noformat}
Default value is: ${project.scm.connection}.
User property is: connectionUrl.
{noformat}

project.scm.connection is not the name of the parameter you can use via the commandline, that is connectionUrl.
In this case you can change the value by either -DconnectionUrl=myNewConnectionUrl or by overriding the value in the properties of the pom.xml:

{code:xml}
<properties>
  <connectionUrl>myNewConnectionUrl </connectionUrl>
</properties>
{code}

The ${project.scm.connection} is a read-only field and represents the path in the pom.xml, so it uses the connection value of the scm-section in <project>

> Documentation for release plugin has still not been corrected.
> --------------------------------------------------------------
>
>                 Key: MRELEASE-983
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-983
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.5.3
>            Reporter: Justin Grant
>            Assignee: Robert Scholte
>            Priority: Minor
>
> Per MRELEASE-707, the documentation at http://maven.apache.org/maven-release/maven-release-plugin/usage.html has still not been corrected, even though the issue was marked as "closed".  It is not an unreasonable expectation as this is supported by the SCM plugin: http://maven.apache.org/components/scm/maven-scm-plugin/status-mojo.html and the other Maven Lifecycle plugins: 
> https://maven.apache.org/scm/maven-scm-plugin/validate-mojo.html
> I'm still a little unclear as to why this is so ridiculous that you would take this information as a parameters (for example, cases of releasing to a different repository than is in your pom), but the documentation should be corrected either way.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)