+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ás Cservenák
<[email protected]>:
I think yes, maven repository is designed for "quick turnaround" in mind:
as soon something is deployed, should be available to others.
In every case, the artifact should go first, and just then the metadata
(that references the artifact)...
On Fri, Jan 8, 2016 at 10:29 AM Dan Tran <[email protected]> wrote:
Hi
My maven POM module has a couple of artifacts to be deployed. Here is
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.xml
[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.xml
(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 while
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: [email protected]
For additional commands, e-mail: [email protected]