Bug#1011775: jamm: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests

[tony mancill]

On Mon, Aug 15, 2022 at 03:59:54PM +0300, Andrius Merkys wrote:
> Hello,
> 
> On Thu, 26 May 2022 18:48:29 +0200 Emmanuel Bourg <ebourg at apache.org> wrote:
> > jamm fails to build with OpenJDK 17, the tests make an illegal
> > reflective access into java.base/java.lang:
> 
> [snip]
> 
> How can I reproduce this FTBFS? The build succeeds on sid now.

Hi Andrius,

The reason you don't see the FTBFS is because the default-jdk in sid
(source package is java-common [1]) still depends on openjdk-11.  The
version in experimental [2] will pull in openjdk-17.

For my local development, I have a schroot with the JDK already
installed (which saves a lot of time during the build) and also created
one for experimental - i.e.:

  jdk-exp-amd64-sbuild
  jdk-sid-amd64-sbuild

For what it's worth, I took a look at the upstream repo and the failing
tests.  One of them can be resolved by changing the maven-compiler-plugin
source and target from 1.6 to 11.  I tried the suggestion in [3] of
adding --add-opens, but it doesn't resolve the (2) remaining test failures.

As best as I can tell, the issue with the tests should be addressed
upstream.  (It would also be nice to get a tag into the repo for 0.4.0,
although that is going to require some tweaking before it will build on
Java 17 too.  There is an open issue for the lack of recent tags too
[4].)

Cheers,
tony

[1] https://tracker.debian.org/pkg/java-common
[2] https://tracker.debian.org/news/1227476/accepted-java-common-072exp2-source-into-experimental/
[3] https://github.com/jbellis/jamm/issues/48
[4] https://github.com/jbellis/jamm/issues/43
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20220815/6bf32951/attachment-0001.sig>