[
https://issues.apache.org/jira/browse/MRELEASE-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350416#comment-15350416
]
Peter Hansson edited comment on MRELEASE-957 at 6/27/16 5:08 AM:
-----------------------------------------------------------------
There should be a general section somewhere in the documentation about "SCM
authentication".
This section should describe the various methods for SCM authentication.
1. username/password on the command line
2. old-school matching of the SCM's hostname against the <id> from the server
section in settings.xml. This has worked also prior to release 2.3 and is - as
far as I know - still in effect if no property 'project.scm.id' is found. IMHO
the 'project.scm.id' property approach should be favored over this approach
(unless you for some reason must use an older version of the
maven-release-plugin)
3. And finally the new method: The special named property 'project.scm.id'. I
believe it works like this: If a property of this name is found in the project
then this value is used for matching against an <id> in servers from
settings.xml. If such a property is not found then method 2 applies. Again,
this is what I think happens. This feature was introduced in version 2.3 of the
maven-release-plugin. (most people today use Maven 3.0.5 which by default uses
version 2.0 of the maven-release-plugin, so many, many Maven users will need to
override maven-release-plugin version to get this to work)
There may be other methods that I'm not familiar with, e.g. SSH key based
methods for SCMs where that is relevant. I'm not sure if we need to describe
such native methods or stick to only describing the ones that have been
explicitly implemented in the maven-release-plugin.
Peter
was (Author: phansson):
There should be a general section somewhere in the documentation about "SCM
authentication".
This section should describe the various methods for SCM authentication.
1. username/password on the command line
2. old-school matching of the SCM's hostname against the <id> from the server
section in settings.xml. This has worked also prior to release 2.3 and is - as
far as I know - still in effect if no property 'project.scm.id' is found. IMHO
the 'project.scm.id' property approach should be favored over this approach
(unless you for some reason must use an older version of the
maven-release-plugin)
3. And finally the new method: The special named property 'project.scm.id'. I
believe it works like this: If a property of this name is found in the project
then this value is used for matching against an <id> in servers from
settings.xml. If such a property is not found the method 2 applies. Again, this
is what I think happens. This feature was introduced in version 2.3 of the
maven-release-plugin. (most people today use Maven 3.0.5 which by default uses
version 2.0 of the maven-release-plugin, so many, many Maven users will need to
override maven-release-plugin version to get this to work)
There may be other methods that I'm not familiar with, e.g. SSH key based
methods for SCMs where that is relevant. I'm not sure if we need to describe
such native methods or stick to only describing the ones that have been
explicitly implemented in the maven-release-plugin.
Peter
> Document how you can use multiple identities on same SCM host
> -------------------------------------------------------------
>
> Key: MRELEASE-957
> URL: https://issues.apache.org/jira/browse/MRELEASE-957
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 2.5.3
> Reporter: Karl Heinz Marbaise
>
> It is unfortunately hard to find how you can handle multiple identities on
> same SCM host. This should be documented in a more prominent location on the
> site and not only mentioned in FAQ with not enough explanations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
