maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tamsin Slinn (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-136) -Dproject.scm.developerConnection=... can not be provided on the command line
Date Wed, 05 Jun 2013 10:12:03 GMT

    [ https://jira.codehaus.org/browse/MRELEASE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326236#comment-326236
] 

Tamsin Slinn commented on MRELEASE-136:
---------------------------------------

This seems to still be the case. Is there any workaround for this? With distributed version
control systems and open source projects which can be forked and merged, it would be really
helpful if the scm details did not have to be hard coded in the pom.

I'm testing with 2.4.1
                
> -Dproject.scm.developerConnection=... can not be provided on the command line
> -----------------------------------------------------------------------------
>
>                 Key: MRELEASE-136
>                 URL: https://jira.codehaus.org/browse/MRELEASE-136
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: documentation, prepare, scm
>    Affects Versions: 2.0-beta-4
>            Reporter: Gilles Scokart
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message