CODEWITHSUNDEEP
mavenrepositoryartifactorysha1
Frederik Koenig
Frederik Koenig

Reputation: 11

Artifactory: Uploaded artifacts do not have a md5 and sha1 file anymore

After we updated JFrog Artifactory we realised that all uploaded artifacts could be uploaded with related .pom file.

But usually the maven-directory contained 4 files: 1. Our uploaded .jar/.war file 2. related .pom file 3. .sha1 file 4. .md5 file

  1. and 4. are missing now. Is there any setting I've overseen? all documentation from JFrog tells me, it should be generated automatically.

Upvotes: 1

Views: 3271

Answers (2)

danf
danf

Reputation: 2709

Artifactory started 'hiding' these files as part of RTFACT-6962 where they were deemed mostly unnecessary since only a handful of legacy clients even care about them (i.e. old maven which also uses the browsing api they appear in) .

If they matter to you they can be 'brought back' by adding the property artifactory.ui.hideChecksums=false to your system.properties file.

As @DarthFennec mentioned these are not actually files, rather they are checksum string that are generated from the artifact's checksum each time you trigger the .md5 .sha1 or .sha2 endpoints for a certain path.

Upvotes: 1

DarthFennec
DarthFennec

Reputation: 2770

These files are sort of "phantom" files. They don't show up in the directory, but if you request them using the REST API you'll get the expected response. For any existing file foo.bar, requesting foo.bar.md5, foo.bar.sha1, or foo.bar.sha256 will provide the appropriate checksum, even though those files don't actually exist.

I think this makes more sense than autogenerating these files for every artifact. Since they do exist for every artifact in every repository, they don't actually provide useful information in the UI, so it just becomes needless clutter.

Upvotes: 1

Related Questions