Samuel Thibault, le jeu. 19 juil. 2018 23:13:26 +0200, a ecrit: > Samuel Thibault, le jeu. 19 juil. 2018 23:00:04 +0200, a ecrit: > > What I think is still missing is "to be loaded by > > java.util.ServiceLoader". How is that supposed to happen? > > > > To make it work, Fridrich Strba says in > > http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2017-November/038927.html > > that he is apparently relinking jdk itself to include > > java-atk-wrapper.jar as a module. Are we really supposed to be doing > > that in Debian? That's mean a circular dependency between openjdk > > and java-atk-wrapper... But otherwise, how are we supposed to make > > the jvm know that for that accessibility provider it should load > > java-atk-wrapper.jar? > > Or put another way: how are we supposed to make the > module contained in java-atk-wrapper.jar ("provides > javax.accessibility.AccessibilityProvider with > org.GNOME.Accessibility.AtkProvider;") visible to the JVM? Is there a > directory where it looks for them?
Of course there is the -p option and alike, but the goal is that it just works without the user having to specify anything. Or should Debian define a module path were the java-atk-wrapper package should put its module? I'd be surprised that openjdk doesn't already define one, just like it used to define the ext/ directory for the older mechanism. Samuel
