Re: RFR: 8296734: JarVerifier:: mapSignersToCodeSource should cache in map [v2]

2022-11-18 Thread pandaapo
On Fri, 18 Nov 2022 15:38:47 GMT, Weijun Wang wrote: >> pandaapo has updated the pull request with a new target base due to a merge >> or a rebase. The incremental webrev excludes the unrelated changes brought >> in by the merge/rebase. The pull request contains three additional commits >> sin

Re: RFR: 8296734: JarVerifier:: mapSignersToCodeSource should cache in map [v2]

2022-11-18 Thread Weijun Wang
On Fri, 18 Nov 2022 03:57:32 GMT, pandaapo wrote: >> The cache named `signerToCodeSource` in `JarVerifier` is never used now. > > pandaapo has updated the pull request with a new target base due to a merge > or a rebase. The incremental webrev excludes the unrelated changes brought in > by the

Re: RFR: 8296734: JarVerifier:: mapSignersToCodeSource should cache in map [v2]

2022-11-18 Thread Weijun Wang
On Fri, 18 Nov 2022 03:57:32 GMT, pandaapo wrote: >> The cache named `signerToCodeSource` in `JarVerifier` is never used now. > > pandaapo has updated the pull request with a new target base due to a merge > or a rebase. The incremental webrev excludes the unrelated changes brought in > by the

Re: RFR: 8296734: JarVerifier:: mapSignersToCodeSource should cache in map [v2]

2022-11-18 Thread Weijun Wang
On Fri, 18 Nov 2022 03:57:32 GMT, pandaapo wrote: >> The cache named `signerToCodeSource` in `JarVerifier` is never used now. > > pandaapo has updated the pull request with a new target base due to a merge > or a rebase. The incremental webrev excludes the unrelated changes brought in > by the

Re: RFR: 8296734: JarVerifier:: mapSignersToCodeSource should cache in map [v2]

2022-11-17 Thread pandaapo
> The cache named `signerToCodeSource` in `JarVerifier` is never used now. pandaapo has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains three additional com