Return-Path: 
 <issues-return-6646-apmail-continuum-issues-archive=continuum.apache.org@continuum.apache.org>
X-Original-To: apmail-continuum-issues-archive@www.apache.org
Delivered-To: apmail-continuum-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 05FDC109FF
	for <apmail-continuum-issues-archive@www.apache.org>;
 Sat, 28 Feb 2015 18:54:15 +0000 (UTC)
Received: (qmail 24045 invoked by uid 500); 28 Feb 2015 18:54:15 -0000
Delivered-To: apmail-continuum-issues-archive@continuum.apache.org
Received: (qmail 24015 invoked by uid 500); 28 Feb 2015 18:54:14 -0000
Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@continuum.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@continuum.apache.org>
List-Post: <mailto:issues@continuum.apache.org>
List-Id: <issues.continuum.apache.org>
Reply-To: dev@continuum.apache.org
Delivered-To: mailing list issues@continuum.apache.org
Received: (qmail 24004 invoked by uid 99); 28 Feb 2015 18:54:14 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Feb 2015 18:54:14 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [199.193.192.100] (HELO codehaus01.managed.contegix.com)
 (199.193.192.100)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Feb 2015 18:53:49 +0000
Received: from codehaus01 (localhost.localdomain [127.0.0.1])
	by codehaus01.managed.contegix.com (Postfix) with ESMTP id 306B4B1171
	for <issues@continuum.apache.org>; Sat, 28 Feb 2015 12:53:18 -0600 (CST)
Date: Sat, 28 Feb 2015 12:53:18 -0600 (CST)
From: "Brent N Atkinson (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Message-ID: 
 <JIRA.116965.1288102434756.22272.1425149598194@codehaus01.managed.contegix.com>
In-Reply-To: <JIRA.116965.1288102434756@codehaus01.managed.contegix.com>
References: <JIRA.116965.1288102434756@codehaus01.managed.contegix.com>
Subject: [jira] (CONTINUUM-2578) Consult settings.xml for credentials when
 fetching maven metadata
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 22cf62d5d84cf5bea94eb3b65e0ebd09
X-Virus-Checked: Checked by ClamAV on apache.org


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

Brent N Atkinson commented on CONTINUUM-2578:
---------------------------------------------

I have updated the issue's description to reflect what I now understand about the issue. Only maven projects should be affected because shell and ant projects use maven-scm to fetch their contents and that already uses settings. 

The problem appears to be that the {{AbstractContinuumProjectBuilder}} fetches the metadata using http, but only uses the credentials as specified. The fix would be to make the builder aware of settings and consult it when there credentials are not specified.

> Consult settings.xml for credentials when fetching maven metadata
> -----------------------------------------------------------------
>
>                 Key: CONTINUUM-2578
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2578
>             Project: Continuum
>          Issue Type: New Feature
>            Reporter: Luca
>            Assignee: Brent N Atkinson
>             Fix For: 1.5.0
>
>         Attachments: configure-scm-credentials-from-settings.diff
>
>
> The attached patch is to configure the scm username/password from settings.xml when building a project from a pom file. It attempts to match the SCM server host name to the id of a server in the <servers> section.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)