Archiva

upload action may not always create a checksum

Details

  • Type: Bug Bug
  • Status: Reopened Reopened
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.3.2
  • Fix Version/s: None
  • Component/s: Web Interface
  • Labels:
    None
  • Number of attachments :
    0

Description

the upload interface is expected to create checksums for the POM and artifact. However, if the artifact is not in the artifacts list (repository scanning), and the create-missing-checksums consumer is enabled, then the checksum will not be created for the new artifact.

The action should create the checksums if this is the case.

It may be best for the upload form to validate the type against the list of artifacts to avoid any confusion as well.

Issue Links

supercedes

Bug - A problem which impairs or prevents the functions of the product. MRM-1429 Proxying of xml files from one archiva server to another fails, when jar files succeed

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Hide
Permalink
Dan Armbrust added a comment -

Got bit by this today as I was uploading files with non-standard file extensions. Only stumbled onto the workaround by accident (adding the extension to the repo-scanning setup)

Show
Dan Armbrust added a comment - Got bit by this today as I was uploading files with non-standard file extensions. Only stumbled onto the workaround by accident (adding the extension to the repo-scanning setup)

People

  • Assignee:
    Unassigned
    Reporter:
    Brett Porter
Vote (1)
Watch (1)

Dates

  • Created:
    Updated: