On 2016-04-04 13:34, Alan Bateman wrote:
On 04/04/2016 12:04, Erik Joelsson wrote:
Makefile looks good.
If you move Java_sun_rmi_transport_GC_maxObjectInspectionAge out of
libjava, should you also remove it from the mapfile for libjava?
Yes, libjava/mapfile-vers will need to be updated t
On 04/04/16 12:34, Alan Bateman wrote:
> On 04/04/2016 12:04, Erik Joelsson wrote:
>> Makefile looks good.
>>
>> If you move Java_sun_rmi_transport_GC_maxObjectInspectionAge out of
>> libjava, should you also remove it from the mapfile for libjava?
>>
> Yes, libjava/mapfile-vers will need to be up
On 04/04/2016 12:04, Erik Joelsson wrote:
Makefile looks good.
If you move Java_sun_rmi_transport_GC_maxObjectInspectionAge out of
libjava, should you also remove it from the mapfile for libjava?
Yes, libjava/mapfile-vers will need to be updated too. It otherwise
looks okay to me, just a p
Makefile looks good.
If you move Java_sun_rmi_transport_GC_maxObjectInspectionAge out of
libjava, should you also remove it from the mapfile for libjava?
/Erik
On 2016-04-04 12:26, Chris Hegarty wrote:
[ including build-dev ]
sun.misc.GC is not "Critical APIs", as defined by JEP 260, so sh
[ including build-dev ]
sun.misc.GC is not "Critical APIs", as defined by JEP 260, so should
be moved out of sun.misc and placed into a more appropriate package,
where it can be encapsulated.
Since GC is only used by RMI, I proposed to move it to the java.rmi
module. Since it has a native compo
