When using the nexusArtifactUploader step, if the specified artifact file attribute contains a trailing whitespace the nexus artifact uploader fails with a "file doesn't exists" message. While being true (the file with the specified name does not acutally exist), it is difficult to troubleshoot when scripting pipelines and the specified artifact name happens to have a trailing whitespace which other steps / calls accept. It would be a nice to have if the nexus-artifact-plugin could perform a trim on the string.

The plugin project does not seem to contain any tests, but this can be reproduced by specifying an existing file in the workspace followed by a trailing line break.