Hmmm, and fixed by me along time ago :|
The question didn't ring a bell, but the answer seems to be at the right
place, the FAQ :)
Be aware that this is a maven-release-plugin specific fix, other related
plugins need to fix this by themselves since the scm section in the pom is
missing the i
Hi Peter,
On 6/26/16 10:00 PM, Peter Hansson wrote:
I can't believe no one has pointed me to the 'project.scm.id' feature which was
> introduced with maven-release-plugin v2.3.
> This is exactly what I wanted.
See :
https://issues.apache.org/jira/browse/SCM-826?focusedCommentId=15350211&page=
I can't believe no one has pointed me to the 'project.scm.id' feature which was
introduced with maven-release-plugin v2.3. This is exactly what I wanted.
See :
https://issues.apache.org/jira/browse/SCM-826?focusedCommentId=15350211&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpa
Ok, so adding to section in POM would be an acceptable path to
a solution?
Consider the following:
scm:hg:https://bitbucket.org/greatness/ambiance
scm:hg:https://bitbucket.org/greatness/ambiance
https://bitbucket.org/greatness/ambiance
bitbucke
Hi,
> 1. Running several *different* flavours of SCMs on the same host. Say you
> have a host called "repohost" which is both an SVN and a Git host. Ok, not
> very likely, but alas not something possible today.
FYI, Github does just that. In particular, they support "git clone" and
"svn checkou
I understand the issue in MNG-5265 as it relates to Maven repos but don't see
how it relates to . Foreign sections don't just pop into your POM by
accident. sections cannot be inherited from dependency resolution as is
the case with Maven repos. Have I misunderstood ?
Peter
On Thursday,
Hi Peter,
there are several issues related to this, just filter in JIRA on the
component Settings[1]
One of the issues I like is MNG-5265[1] which explains that id is not
secure enough, a simple typo might lead to leaking your credentials to the
wrong party.
So the solution is probably not
Hello
I've been looking at improving the way certain plugins (scm, release, etc)
lookup credentials from a in settings.xml in order to find the
credentials to use for a given endpoint.
The current method - largely undocumented - is that the hostname from
endpoint's URL must match the server id
