Re: Same snapshot deploy number for entire build - possible

2019-09-15 Thread Tamás Cservenák
@Dan see here https://github.com/apache/maven/blob/master/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/RemoteSnapshotMetadata.java On Mon, Sep 16, 2019, 00:35 Dan Tran wrote: > Please keep in mind QA is not a maven user. All download/deployment and > testing are

Re: Same snapshot deploy number for entire build - possible

2019-09-15 Thread Dan Tran
Please keep in mind QA is not a maven user. All download/deployment and testing are mostly automated, however, when come to reporting they have to use something concrete which is the exact snapshot downloaded for them They also come to accept that each artifact has its own buildNo/snapshotNo,

Re: Same snapshot deploy number for entire build - possible

2019-09-15 Thread Tibor Digana
Hi Francois and Dan, I understood it the same way as Francois mentioned. Not sure if NN in the format "artifactId-version-timestamp-NN" is a bug. Who cares is probably someone who downloads the artifact manually, maybe the QA. Also downloading the artifacts from Nexus never was so trivial for QA

Re: Same snapshot deploy number for entire build - possible

2019-09-15 Thread Francois Marot
I'm sorry to insist but nevertheless I insist ;). I may have misunderstood the problem but as I understand it, the whole problem can be sumed up by: " the fact that the repository adds a number at the end of the deployed files is a problem because not all artifacts deployed from the same reactor