[9] RFR 8130181: Deprecate java.security.Provider(String, double, String), add Provider(String, String, String)
Wang Weijun
weijun.wang at oracle.com
Fri Jun 24 01:59:08 UTC 2016
- Previous message (by thread): [9] RFR 8130181: Deprecate java.security.Provider(String, double, String), add Provider(String, String, String)
- Next message (by thread): [9] RFR 8130181: Deprecate java.security.Provider(String, double, String), add Provider(String, String, String)
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
If you mandate the use of Verona version style, can we just use the Version class in the constructor?
> On Jun 24, 2016, at 9:56 AM, Valerie Peng <valerie.peng at oracle.com> wrote:
>
>
> Well, we have to define something for the version syntax and how it converts to the legacy double version.
> I think it makes sense to follow the Verona JEP as that's the JDK version syntax which seems to fit the normal convention of release numbering.
>
> Maybe we can clarify major and minor by referring to java.lang.Runtime.Version class?
> Valerie
- Previous message (by thread): [9] RFR 8130181: Deprecate java.security.Provider(String, double, String), add Provider(String, String, String)
- Next message (by thread): [9] RFR 8130181: Deprecate java.security.Provider(String, double, String), add Provider(String, String, String)
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the security-dev
mailing list