search

payara / Payara_PatchedProjects

6 stars 25 forks source link

FISH-48 HK2 release 2.6.1.payara-p3 #323

Closed jGauravGupta closed 4 years ago

jGauravGupta commented 4 years ago

Signed-off-by: Gaurav Gupta gaurav.gupta@payara.fish

Depends on

https://github.com/payara/patched-src-hk2/pull/15 https://github.com/payara/patched-src-hk2/pull/16

pzygielo commented 4 years ago

@MattGill98 @jGauravGupta - plenty of files have mismatch between checksums declared in corresponding file and calculated, for both MD5 and SHA1. For example: 

curl --silent https://raw.githubusercontent.com/jGauravGupta/Payara_PatchedProjects/b40274ffee79aa3c88eaf1402733571a4dc29ed5/org/glassfish/hk2/caching-aop-example-runner/2.6.1.payara-p3/caching-aop-example-runner-2.6.1.payara-p3.pom | sha1sum
0dcfe727fd0f7f4a7aa9eba3d17d12934c306956
curl --silent https://raw.githubusercontent.com/jGauravGupta/Payara_PatchedProjects/b40274ffee79aa3c88eaf1402733571a4dc29ed5/org/glassfish/hk2/caching-aop-example-runner/2.6.1.payara-p3/caching-aop-example-runner-2.6.1.payara-p3.pom.sha1
12540d10196d189c052a3fcb8b69cb62741032a6

(74 files per algorithm).

It results in warning described in #305, #302, and also reported as #283 (with a bunch other not reported). Is that only on my end, and noone on your side bothers to fix the process used?