You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Justin Grant (JIRA)" <ji...@apache.org> on 2017/03/20 17:44:42 UTC
[jira] [Created] (MRELEASE-983) Documentation for release plugin
has still not been corrected.
Justin Grant created MRELEASE-983:
-------------------------------------
Summary: 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
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
(v6.3.15#6346)