auo / mvn-up Goto Github PK

I use mvn-up to upload portlet jar artifact to nexus.
The file of the hash (md5 and sha1) uploaded into nexus does not match with the hash computed by nexus itself.

In jar attributes I see the correct hash;

Checksum

The sha1 file uploaded contains a9ceab9748921246b5dc46ded5835e7e9b948d3e and md5 file contains ace03f005c056a89bd2cc4d5f8c174ed.

Hi,

I use mvn-up to deploy a .zip artifact to a private JFrog artifactory.
However, JFrog responds with Http 404 Not Found.

I noticed that mvn-up sends the check-files (md5 and sha1) before the actual artifact file, so it tries to send the files in this order:
myartifact.zip.md5
myartifact.zip.sha1
myartifact.zip
leading to the 404-Response from JFrog when receiving the md5-file. (I guess JFrog is looking for a matching artifact when it receives a checksum)

When I change the order of the sent files in maven-upload.js by switching these lines (linenumber 38 and 40):

        files.push({ path: artifactPath, content: null, location: file });
        await createCheckFiles(fs.createReadStream(file), artifactPath, files);

the upload to JFrog works fine.

Could you please change the order, so the upload works in JFrog?

Thank you in advance,
Christian

Current implementation alwasy creates pom.xml file for single upload invocation. This works well when there is only one artifact for given groupId and artifactId. However, maven repository allows to upload many artifacts using classifier concept e.g. test, javadoc etc.
Currently, it is impossible to execute many upload for the same groupId and artifactId with different classifier because pom.xml is created for 1st upload - assuming this is release repository and override is disabled.

How to improve it? Give possibility to upload many artifact as single invocation or flat to not generate pom.xml.