just to clarify things - we are the vendor of the libraries and looking
for a simple way to keep all provided features for a Java 9 compatible
release. Otherwise our lib users have to specify XaddExports which is
pretty annoying. Additionally it would simplify providing workarounds
for JDK issues as we often did in the past until things get fixed (if
they get fixed).
-Wolfgang
Am 12.05.2016 um 09:24 schrieb Alan Bateman:
On 12/05/2016 08:15, wzberger wrote:
some of our libraries (third party vendor) require access to some
internal API methods. Is it possible to add XaddExports to a library
in a way that it is transparent for the user of the lib - means the
related package must not be specified by the user via XaddExports?
No, as that would that make it too easy for every library to break
into JDK internals. I don't know what 3rd party libraries you have but
best to get bugs submitted to the maintainers to look at these issues.
-Alan.