Maven Upload Requests

Upload cobertura 1.9 to central

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Resolution: Fixed
  • Labels:
    None

Description

Upload cobertura-1.9 to central.
(Look for related cobertura-runtime 1.9 MAVENUPLOAD request too)

Issue Links

is depended upon by

Bug - A problem which impairs or prevents the functions of the product. MAVENUPLOAD-1618 Upload cobertura-runtime 1.9 to central

  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Henri Yandell added a comment -
Done.
Show
Henri Yandell added a comment - Done.
Hide
Permalink
Joakim Erdfelt added a comment -
Reopening.
Uploaded Artifact is not official 1.9 binary. (origin unknown)

http://joakim.erdfelt.com/maven/cobertura-1.9-bundle.jar

Bundle at URL above has been verified as correct.

Correct bundle has following sha1sum ...
c5d057b940a843e484f696b8c4c35e4bbe5e947a cobertura-1.9-bundle.jar

Official binary - cobertura-1.9.jar should have the following sha1 and md5 hashcodes ...
sha1: fe3dd9ef4bc8ce13a6c69c22f9d92aca1cec33a8
md5: f3d25c4ed63bfc7241407ed211a9b527
Show
Joakim Erdfelt added a comment - Reopening. Uploaded Artifact is not official 1.9 binary. (origin unknown) http://joakim.erdfelt.com/maven/cobertura-1.9-bundle.jar Bundle at URL above has been verified as correct. Correct bundle has following sha1sum ... c5d057b940a843e484f696b8c4c35e4bbe5e947a cobertura-1.9-bundle.jar Official binary - cobertura-1.9.jar should have the following sha1 and md5 hashcodes ... sha1: fe3dd9ef4bc8ce13a6c69c22f9d92aca1cec33a8 md5: f3d25c4ed63bfc7241407ed211a9b527
Hide
Permalink
Carlos Sanchez added a comment -
we shouldn't change it now, people already have it in their local repo. The only thing would be to upload a 1.9-1 with the right one
Show
Carlos Sanchez added a comment - we shouldn't change it now, people already have it in their local repo. The only thing would be to upload a 1.9-1 with the right one
Hide
Permalink
Brett Porter added a comment -
can we delete the 1.9 as bad and put this up as 1.9-1 then?
Show
Brett Porter added a comment - can we delete the 1.9 as bad and put this up as 1.9-1 then?
Hide
Permalink
Carlos Sanchez added a comment -
seems that I misunderstood Joakim and the one in the repo is not the one he provided, so I need to take a look first.
Show
Carlos Sanchez added a comment - seems that I misunderstood Joakim and the one in the repo is not the one he provided, so I need to take a look first.
Hide
Permalink
Joakim Erdfelt added a comment -
The one in the repo is bad, and/or suspect.
It is not the official binary.
No idea where it came from.

Brett's solution has merit.
Eliminate the bad/suspect binary, and create a new version 1.9-1 with the correct binary.

Do you need a new bundle created for that? (new MAVENUPLOAD request too)
Show
Joakim Erdfelt added a comment - The one in the repo is bad, and/or suspect. It is not the official binary. No idea where it came from. Brett's solution has merit. Eliminate the bad/suspect binary, and create a new version 1.9-1 with the correct binary. Do you need a new bundle created for that? (new MAVENUPLOAD request too)
Hide
Permalink
Carlos Sanchez added a comment -
all files in the server have same date and time, in both m1 and m2 repos, and match the time the jira was closed by Henry, so if it weren' t Joakim I'd say he provided the wrong one ;)

i changed the jar (backup in repository-removed dir) and added a README file
Show
Carlos Sanchez added a comment - all files in the server have same date and time, in both m1 and m2 repos, and match the time the jira was closed by Henry, so if it weren' t Joakim I'd say he provided the wrong one ;) i changed the jar (backup in repository-removed dir) and added a README file

People

  • Assignee:
    Carlos Sanchez
    Reporter:
    Joakim Erdfelt
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: