[MGPG-129] sign-and-deploy-file incorrectly renames source files when deployed.

**[Lee Rhodes](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=leerho)** opened **[MGPG-129](https://issues.apache.org/jira/browse/MGPG-129?redirect=false)** and commented

You can see from the Debug_output.txt (line 209) that the source files are of the form: "datasketches-memory-3.0.0.jar", "datasketches-memory-3.0.0-tests.jar", etc.

But the files being deployed (line 252) are of the form: "datasketches-memory-root-3.0.0.jar", etc. This extra "-root" is incorrect.

How do I fix this so that the given files are just signed and deployed without being renamed?

This can be replicated from the open-source site: https://github.com/apache/datasketches-memory/tree/3.0.X.
First run the "package-multi-release-jar.sh", which creates the source files under /target/. Then run the script "sign-deploy-jar.sh" with inputs "3.0.0" \. You will need an account on Nexus.

BTW, the source file names have to be different from the root project name because the source files are MR-Jars that have been assembled by the above "package-multi-release-jar.sh".

"sign-and-deploy-file" does not just sign and deploy the given source files, it is also renaming them, which causes the deployed files to have incorrect names.

---

**Affects:** 3.0.1, 3.2.3, 3.2.4

**Attachments:**
- [Debug_output.txt](https://issues.apache.org/jira/secure/attachment/13070433/Debug_output.txt) (_30.29 kB_)
- [package-multi-release-jar.sh](https://issues.apache.org/jira/secure/attachment/13070431/package-multi-release-jar.sh) (_8.72 kB_)
- [pom.xml](https://issues.apache.org/jira/secure/attachment/13070432/pom.xml) (_18.92 kB_)
- [sign-deploy-jar.sh](https://issues.apache.org/jira/secure/attachment/13070434/sign-deploy-jar.sh) (_2.84 kB_)

Start by reviewing the attached sign-deploy-jar.sh, package-multi-release-jar.sh, pom.xml, and Debug_output.txt, then reproduce the behavior in the datasketches-memory 3.0.X project. Trace how sign-and-deploy-file handles the supplied artifact names; done means the files are signed and deployed without the extra "-root" component, with the expected names preserved.

Written by the indexing model from the issue text.