-
Bug
-
Resolution: Fixed
-
P4
-
8u201, 10
-
b40
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8195702 | 11 | Volker Simonis | P4 | Resolved | Fixed | b01 |
JDK-8197731 | 10u-cpu | Volker Simonis | P4 | Resolved | Fixed | master |
JDK-8200973 | 10.0.2 | Unassigned | P4 | Resolved | Fixed | b01 |
JDK-8195941 | 10.0.1 | Volker Simonis | P4 | Resolved | Fixed | b01 |
JDK-8220047 | openjdk8u212 | Volker Simonis | P4 | Resolved | Fixed | b01 |
It is clear that "java.specification.vendor" and "java.vm.specification.vendor" have to be equal to "Oracle Corporation" as long as Oracle leads the corresponding platform JSRs. Besides that, every OpenJDK distributor should be able to set 'java.vendor' and 'java.vm.vendor' according to his needs. Note that there are also additional "vendor" properties like "java.vendor.url" and "java.vendor.url.bug" which really only make sense if customized by the corresponding distributor.
Making these properties configurable at runtime is tracked by
- backported by
-
JDK-8195702 [test] runtime/6981737/Test6981737.java shouldn't check 'java.vendor' and 'java.vm.vendor' properties
- Resolved
-
JDK-8195941 [test] runtime/6981737/Test6981737.java shouldn't check 'java.vendor' and 'java.vm.vendor' properties
- Resolved
-
JDK-8197731 [test] runtime/6981737/Test6981737.java shouldn't check 'java.vendor' and 'java.vm.vendor' properties
- Resolved
-
JDK-8200973 [test] runtime/6981737/Test6981737.java shouldn't check 'java.vendor' and 'java.vm.vendor' properties
- Resolved
-
JDK-8220047 [test] runtime/6981737/Test6981737.java shouldn't check 'java.vendor' and 'java.vm.vendor' properties
- Resolved
- relates to
-
JDK-8189761 COMPANY_NAME, IMPLEMENTOR, BUNDLE_VENDOR, VENDOR, but no configure flag
- Resolved