Am 12.05.2016 um 15:17 schrieb 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
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. S
On 12/05/2016 08:47, wzberger wrote:
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 sim
On 12/05/2016 08:47, wzberger wrote:
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 simp
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 issu
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 X
