-
Bug
-
Resolution: Duplicate
-
P3
-
None
-
10
As part JCK AutoSig activity, I am checking the difference between sequential JDK 10 build API signatures from which I noticed that
constructors of many protected APIs under javax.lang.model.* package were changed to add “since =9” to the Deprecated type of the corresponding constructors.
Change set in JDK10 build 30: (see the comment [1] )
JBS issue responsible for the change which does not have a relevant CSR request:JDK-8172818
The aforementioned changes do not have a CSR request filed in JCK10 .
As per the CCC charter I read,
(1) Every change to the specification of an exported interface, either
external or private, requires a CCC request regardless of the size of
the change.
I believe this applies to protected API members whose signature is changed.
constructors of many protected APIs under javax.lang.model.* package were changed to add “since =9” to the Deprecated type of the corresponding constructors.
Change set in JDK10 build 30: (see the comment [1] )
JBS issue responsible for the change which does not have a relevant CSR request:
The aforementioned changes do not have a CSR request filed in JCK10 .
As per the CCC charter I read,
(1) Every change to the specification of an exported interface, either
external or private, requires a CCC request regardless of the size of
the change.
I believe this applies to protected API members whose signature is changed.
- duplicates
-
JDK-8196727 Add since=9 deprecation information to javax.lang.model classes
-
- Closed
-
- relates to
-
JDK-8172818 Add since=9 deprecation information to javax.lang.model classes
-
- Resolved
-