Details
-
Bug
-
Resolution: Fixed
-
P3
-
8
-
b64
-
generic
-
generic
-
Verified
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8001707 | 7u40 | Bradford Wetmore | P3 | Closed | Fixed | b01 |
Description
jce.jar/sunjce_provider.jar do have:
Manifest-Version: 1.0^M
Implementation-Vendor: Oracle Corporation^M
Implementation-Title: Java Runtime Environment^M
Implementation-Version: 1.8.0-ea^M
Implementation-Vendor-Id: com.sun^M
Specification-Vendor: Oracle Corporation^M
Specification-Title: Java Platform API Specification^M
Created-By: 1.7.0 (Oracle Corporation)^M
Specification-Version: 1.7^M
Extension-Name: javax.crypto^M
But the others (ec/mscapi/pkcs11/ucrypto) only have:
Manifest-Version: 1.0^M
Created-By: 1.6.0_14 (Sun Microsystems Inc.)^M
Manifest-Version: 1.0^M
Implementation-Vendor: Oracle Corporation^M
Implementation-Title: Java Runtime Environment^M
Implementation-Version: 1.8.0-ea^M
Implementation-Vendor-Id: com.sun^M
Specification-Vendor: Oracle Corporation^M
Specification-Title: Java Platform API Specification^M
Created-By: 1.7.0 (Oracle Corporation)^M
Specification-Version: 1.7^M
Extension-Name: javax.crypto^M
But the others (ec/mscapi/pkcs11/ucrypto) only have:
Manifest-Version: 1.0^M
Created-By: 1.6.0_14 (Sun Microsystems Inc.)^M
Attachments
Issue Links
- backported by
-
JDK-8001707 Makefiles for various security providers aren't including the default manifest.
- Closed
- relates to
-
JDK-8003482 build-infra: Use correct manifest in security jars
- Closed