Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5870C200C4C for ; Mon, 20 Mar 2017 07:36:46 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 57313160B76; Mon, 20 Mar 2017 06:36:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A232D160B81 for ; Mon, 20 Mar 2017 07:36:45 +0100 (CET) Received: (qmail 44681 invoked by uid 500); 20 Mar 2017 06:36:44 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 44670 invoked by uid 99); 20 Mar 2017 06:36:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Mar 2017 06:36:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 43953180A02 for ; Mon, 20 Mar 2017 06:36:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.451 X-Spam-Level: * X-Spam-Status: No, score=1.451 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id dl0T8t5iCVSe for ; Mon, 20 Mar 2017 06:36:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 3EC8C5FE25 for ; Mon, 20 Mar 2017 06:36:43 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E25BFE04FE for ; Mon, 20 Mar 2017 06:36:41 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9765F254CB for ; Mon, 20 Mar 2017 06:36:41 +0000 (UTC) Date: Mon, 20 Mar 2017 06:36:41 +0000 (UTC) From: =?utf-8?Q?J=C3=B6rg_Sesterhenn_=28JIRA=29?= To: issues@maven.apache.org Message-ID: In-Reply-To: References:

Subject: [jira] [Commented] (ARCHETYPE-520) Following mirror configuration from settings.xml for downloading archetype metadata MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 20 Mar 2017 06:36:46 -0000 [ https://issues.apache.org/jira/browse/ARCHETYPE-520?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1= 5932214#comment-15932214 ]=20 J=C3=B6rg Sesterhenn commented on ARCHETYPE-520: ------------------------------------------- [~rfscholte]: Just to be clear on that - the mirrors are used at our site a= s well. They are just not used exclusively which is the problem. Did you use the * setting in your tests? (How) can we= run these integration tests at our site to see if we get the same result? > Following mirror configuration from settings.xml for downloading archetyp= e metadata > -------------------------------------------------------------------------= ---------- > > Key: ARCHETYPE-520 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-520 > Project: Maven Archetype > Issue Type: Bug > Components: Plugin > Affects Versions: 3.0.0 > Reporter: Johannes Siebel > Attachments: maven-archetype-delay.TXT, settings.xml > > > Since using the maven-archetype-plugin with version 3.0.0 the plugin trie= s to connect to _both_ our internal nexus and to {{http://repo.maven.apache= .org}} for downloading Maven artifacts used by Archetypes. Since we are usi= ng a proxy, the generation of the archetype is delayed until the download o= f the Maven artifacts times out. > We'd expect the archetype to only contact our own artifact repository, wi= thout trying to connect to {{http://repo.maven.apache.org}} at all. > I've attached a snippet with the debug output of the archetype:generate g= oal and the configuration of our mirror. > We assume this problem is related to ARCHETYPE-358. -- This message was sent by Atlassian JIRA (v6.3.15#6346)