Hi Mathias, I commented on the pull request. For me it is crucial to be able to upload additional artifacts to a coordinate. It has various reasons. When you work in an agile mind set, you do not need every artifact in the very beginning. You do approach agile and deliver first the most needed part. In case you have a heterogenous development environment that you want to provide with a native library you deliver first your own machines native library…. And then when needed the other machines will follow…
Another much forgotten usage of this additional artifact attachment is, when for example a CVE to a coordinate comes up. At the moment, there is a hard work to maintain the CVEs and related coordinates. It would be great to put a CVE where it belongs… to the coordinate itself These are my 5 cents, I vote +1 Best Regards Kemal > Am 26.05.2023 um 10:10 schrieb Mathias de Riese <math...@de-riese.de>: > > Hey there, > > I did not get a reply to this message. Does that mean, all is fine and you > would like to merge the PR? (Once review comments are handled, of course.) > > Cheers, > Mathias > > On Tue, May 23, 2023, at 11:16, Mathias de Riese wrote: >> Hi, >> >> some time ago I had the problem described in >> https://issues.apache.org/jira/browse/MDEPLOY-118: The company I was >> working wants to build multiple native artifacts of the same software >> on different machines and deploy them. Since additional platforms / >> build hosts may be added later as needed by projects and some software >> stays rather stable, it is desirable to add artifacts for the same >> version over time while preventing re-deploys of artifacts via the repo. >> >> As the same problem was described in the issue, I went ahead and >> implemented it in >> https://github.com/apache/maven-deploy-plugin/pull/28, which >> unfortunately was not merged at the time. >> >> Now, Elliotte remarks that my change might violate Maven repos stare >> decisis properties. My intent was to keep these in place while allowing >> to add artifacts consistently. >> >> The question to you guys is: >> >> Is adding an artifact to an existing deployment a change of the >> deployment in the sense that guarantees are broken? >> >> >> In case you would like to merge my PR, I am willing to do the conflict >> resolution work by now required. Please contact me via the PR or >> directly, in case I loose track of this discussion here, which might >> happen, since I am busy with other stuff right now. >> >> Cheers, >> Mathias de Riese > > -- > Mathias de Riese > math...@de-riese.de > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > GF Kemal Soysal __________________________ Kemal Soysal LS IT-Solutions GmbH kemal.soy...@ls-it-solutions.de Mobil: +49 1512 404 55 66 Marthashof 6 D-10435 Berlin
