There are cases where the filename of an artifact that is attached to the build does not match the filename under which the artifact actually ends up in the repository. When the "artifacts" goal is used, we usually want to calculate hashes for the files that get deployed into the repository. If we use the appendFilename option, then it is usually to be able to run a command like sha512sum -c *.sha512 to check if the hashes for the hashed files are valid. However, if the original filename of the attached artifact differs from the name it ends up under in the repository, then this fails because the filename in the .sha512 file ends up being wrong.
For example, Tycho may attach a file p2content.xml as an artifact to the build such that it gets written to the repository as org.apache.uima.ruta.feature-3.2.0-p2metadata.xml. When we apply checksum-maven-plugin:1.11:artifacts in such a case, we get a file org.apache.uima.ruta.feature-3.2.0-p2metadata.xml.sha512, but its content is:
There are cases where the filename of an artifact that is attached to the build does not match the filename under which the artifact actually ends up in the repository. When the "artifacts" goal is used, we usually want to calculate hashes for the files that get deployed into the repository. If we use the
appendFilenameoption, then it is usually to be able to run a command likesha512sum -c *.sha512to check if the hashes for the hashed files are valid. However, if the original filename of the attached artifact differs from the name it ends up under in the repository, then this fails because the filename in the.sha512file ends up being wrong.For example, Tycho may attach a file
p2content.xmlas an artifact to the build such that it gets written to the repository asorg.apache.uima.ruta.feature-3.2.0-p2metadata.xml. When we applychecksum-maven-plugin:1.11:artifactsin such a case, we get a fileorg.apache.uima.ruta.feature-3.2.0-p2metadata.xml.sha512, but its content is:The content should instead be