How to embedd access to internal API in a library via XaddExports

[Alan Bateman]

On 12/05/2016 09:49, wzberger wrote:
>
> We provide libs for Swing and JavaFX. For most of the issues bug 
> reports have been filed. But it's not only about known bugs we also 
> have to handle unknown bugs - the release cycles until things get 
> fixed are way too long while customers need solutions. So will it be 
> possible to fork specific JDK modules and deploy such modified modules 
> to users in a simple manner - webstart included?
With OpenJDK then you can of course do your own builds. The java.desktop 
module is not an upgradeable module (not like the EE modules) so you 
can't deploy an upgraded version of java.desktop on the upgrade module 
path, at least not with Oracle JDK builds. You can patch it via -Xpatch 
for testing or debugging purposes but I assume you don't want your users 
doing that. This reminds to ask - when you patch the code today then you 
are using -Xbootclasspath/p or does patching mean using core reflection 
to access/change private fields.

Java Web Start is not in OpenJDK so I can't comment on patching that (or 
maybe you mean having web start download patches?).

Finally, and I understand it can frustrating to hit a bug that isn't 
fixed in a timely manner, but have you considered contributing fixes for 
the bugs that you are running into?

-Alan