The source code repository is now mirrored on GitHub and accessible from here. Graphics provided by Geoff Hook. Found another problem while digging into this problem: I think this case differs from ICU version in that it only has "1. Comment 53 David Williams
Uploader: | Netaur |
Date Added: | 18 October 2011 |
File Size: | 31.98 Mb |
Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
Downloads: | 10956 |
Price: | Free* [*Free Regsitration Required] |
The repository can be cloned using either https: Comment 45 Wayne Beaton Please verify that it works so we can close the issue. If those don't work then we should at least have a clear statement of what the "real" problem is. Comment 20 Matthias Sohn Closing this bug since this bpg-jdk15on-147.jar is superseded by bug for adding a newer version of bouncycastle.
And are any of them "old" ones signed by previous cert? We asked the Eclipse foundation to request a JCE signing certificate from Oracle in bug and we requested the signing service to be enhanced bug in order to enable signing with the JCE certificate. Comment 33 Chris Aniszczyk I'd suggest to try the former, first, but haven't thought too deeply about it.

I propose to set provider to "Bouncy Castle" and to change the display names from "bcprov" and "bcpg" to: See bug for more details. I assume should be assigned to Matthias?
Index of /bc/download
Comment 30 Chris Aniszczyk All other BC libs should be fine to have their original signature removed and bcpg-dk15on-147.jar with an own certificate.
View All Add an attachment proposed patch, testcase, etc. Is there another bundle which is using the wrapping technique you mentioned? I only have signed bundles installed. But, I am not very confident.
The first one is a real cost saver as it does not lead to us receiving emails starting with "Our development team has spent some number of weeks trying to work out We'll see, I've started another build to test. The problem is that this third party bundle doesn't behave properly in Eclipse environment giving security exceptions so the thought was to provide it "as is" and that might solve the security exception, but that would imply we could not add the usual "about.
That bundle is commonj. Any expected for Kepler?
But, the "as is" bundle didn't solve the problem anyway, so, we'll need to do more bcpg-jdk15on-147.jr, something else anyway. I just kicked off another build.
Download bcpg-jdk15on-1.47.jar : bcpg « b « Jar File Download
I checked out the sources from the "dev. Again, I'll ask if any status? MF that came from the original bundle. I've bcpg-jdkk15on-147.jar looked at the code that "does the work", but in the other prebuilt cases, the name of the jar in the cvs repo "follows" the name of the bundle.
Download castle JAR files with all dependencies
Now if we can just get back to that point! We'll see if the next build produces non-corrupt versions. It changed approximately March of Please also see the porting guide for advice on porting to this release from much cbpg-jdk15on-147.jar ones release 1.
No repository found containing: While I don't understand the technical issues involved with the "not signed by same provider" issue mentioned elsewhere, I'm wondering if another approach might be to "wrap" the original, unchanged jar, in another bundle, which would do little other than export the original packages. Comment 37 Wayne Beaton
Comments
Post a Comment