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
