[
https://issues.apache.org/jira/browse/MRELEASE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-136.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> -Dproject.scm.developerConnection=... can not be provided on the command line
> -----------------------------------------------------------------------------
>
> Key: MRELEASE-136
> URL: https://issues.apache.org/jira/browse/MRELEASE-136
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: documentation, prepare, scm
> Affects Versions: 2.0-beta-4
> Reporter: Gilles Scokart
> Priority: Major
>
> The developerConnection MUST now be placed in the pom. In the previous
> version, it was possible to give it on the command line. Which was usefull
> when you want to build source stored on a "private" repository, and that you
> don't want to expose the adress of this repository in your sources (in
> pom.xml) that you distribute.
> By the way, the doc still mention it.
> Note also that in a case of a multi-project (without inheritance), the scm
> tag must be placed on all sub-modules as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
