Comments below:
On 04/06/2016 01:53 PM, Alan Bateman wrote:
On 06/04/2016 12:47, Richard Opalka wrote:
BTW: Just looking at the contents of your JAR file then it looks
like this is the EE version of the Common Annotations. In that case
you shouldn't need a multi-release JAR. Instead you should be able
to put the module-info.class in the top level directory and deploy
it on the upgrade module path.
Yes I know. Our requirement is to support both JDK8 and JDK9 with the
same jar.
Thus in my experiments I have javax classes compiled for JDK8 and
module-info.class for JDK9.
Multi-Release jar was my first attempt, when it failed I did what you
propose above Alan.
and did this work? In this case then I would expect the same JAR file
should just work on the upgrade module path with JDK 9 or via the
endorsed standard override mechanism with JDK 8. In the case of the
latter then the module-info.class will be ignored.
Yes, it worked for the usecase (PoC) I'm testing ATM.
My next attempt will be to leverage our testsuite FW
and test it on both JDK8 and JDK9.
-Alan.
Rio
