You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Mathias de Riese <ma...@de-riese.de> on 2022/09/25 16:03:24 UTC
MDEPLOY-118: Contribution still welcome? Alternative solutions?
Hi Maven Developers,
I currently face exactly the situation described in https://issues.apache.org/jira/browse/MDEPLOY-118:
Our MRM (Nexus) was recently configured to prevent re-deployments as a consequence of a mishap. However, we use Maven runs on multiple platforms to deploy an artifact per platform for the same C++-based project. Each run tries to deploy the projects POM. Consequently, the second run trying to deploy its artifact fails.
To me, the solution described in MDEPLOY-118 seems to be superior to any other I came across during my research in the past days. I did write our own Maven plugin, but I am certainly not experienced enough, that I trust my own judgement.
After a bit of looking around in the source code, I thing I might be able to provide a PR for this.
Therefore my question: Is this really (still) something you would like to have in Maven and more specifically in the Deploy Plugin?
I have a rough idea, how I would implement it and would like to present a sketch to someone before completing it. Is the mailing list the right place or are you also paying attention to the Jira comments (of a closed issue)? Or is another communication channel more appropriate?
Thanks in advance for the help / answers! I sure hope, I might help a tiny bit in Maven development.
Cheers,
Mathias