Return-Path: X-Original-To: apmail-maven-users-archive@www.apache.org Delivered-To: apmail-maven-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5AEA418952 for ; Fri, 8 Jan 2016 21:46:01 +0000 (UTC) Received: (qmail 76086 invoked by uid 500); 8 Jan 2016 21:45:59 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 76027 invoked by uid 500); 8 Jan 2016 21:45:59 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 76016 invoked by uid 99); 8 Jan 2016 21:45:59 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jan 2016 21:45:59 +0000 Received: from robertscholte.dynamic.ziggo.nl (5248749D.cm-4-1b.dynamic.ziggo.nl [82.72.116.157]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id D7E4A1A0015 for ; Fri, 8 Jan 2016 21:45:58 +0000 (UTC) Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: "Maven Users List" Subject: Re: maven-metadata.xml should be deployed last References: Date: Fri, 08 Jan 2016 22:45:55 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Robert Scholte" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.17 (Win32) +1 Also interesting to figure out: if upload works in parallel, do we need = to = divide this in two: first pom, main artifact and attached artifacts, = second the metadata files. Or is Aether already aware of this? maven-deploy-plugin 3.0 will use maven-artifact-transfer. Could you make= a = JIRA issue just to track this? thanks, Robert Op Fri, 08 Jan 2016 10:51:45 +0100 schreef Tam=E1s Cserven=E1k = : > I think yes, maven repository is designed for "quick turnaround" in mi= nd: > as soon something is deployed, should be available to others. > In every case, the artifact should go first, and just then the metadat= a > (that references the artifact)... > > On Fri, Jan 8, 2016 at 10:29 AM Dan Tran wrote: > >> Hi >> >> My maven POM module has a couple of artifacts to be deployed. Here i= s = >> the >> order of deployment >> >> [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ >> brs-installer --- >> [INFO] Downloading: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/maven-metadata.xml >> [INFO] Downloaded: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/maven-metadata.xml >> (994 B at 44.1 KB/sec) >> [INFO] Uploading: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/brs-installer-1.0.0-20160108.090346-509.pom >> [INFO] Uploaded: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/brs-installer-1.0.0-20160108.090346-509.pom >> (12 KB at 3.3 KB/sec) >> [INFO] Downloading: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/maven-metadata.xml >> [INFO] Downloaded: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/maven-metadata.xml >> (545 B at 24.2 KB/sec) >> [INFO] Uploading: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/maven-metadata.xml >> [INFO] Uploaded: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/maven-metadata.xml >> (1004 B at 122.6 KB/sec) >> [INFO] Uploading: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/maven-metadata.xml >> [INFO] Uploaded: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/maven-metadata.xml >> (545 B at 2.5 KB/sec) >> [INFO] Uploading: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/brs-installer-1.0.0-20160108.090346-509-build.x= ml >> [INFO] Uploaded: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/brs-installer-1.0.0-20160108.090346-509-build.x= ml >> (14 KB at 86.0 KB/sec) >> [INFO] Uploading: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/maven-metadata.xml >> [INFO] Uploaded: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/maven-metadata.xml >> (1004 B at 140.1 KB/sec) >> [INFO] Uploading: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/brs-installer-1.0.0-20160108.090346-509.ova >> [INFO] Uploaded: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/brs-installer-1.0.0-20160108.090346-509.ova >> (4044494 KB at 34899.1 KB/sec) >> [INFO] Uploading: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/maven-metadata.xml >> [INFO] Uploaded: >> >> http://mycomp.com:8081/myrepo/snapshots/com/mycomp/brs/installer/brs-= installer/1.0.0-SNAPSHOT/maven-metadata.xml >> (1004 B at 98.0 KB/sec) >> >> >> The issue here, after the POM, maven-metadata.xml is followed, the >> subsequent deployments are large artifacts ( ~4G) >> >> The issue here if user attempts to download the latest snapshot whil= e = >> the >> large artifact still in the middle of upload, the download will fail = = >> with >> not found error >> >> Does it make sense to enhance maven deploy plugin to deploy >> maven-metadata.xml last? >> >> Thanks >> >> -Dan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org