Here's what I found out so far about this bug.
Unsetting the DISPLAY environment variable works around the FTBFS error
by skipping the failing Junit tests. However, unsetting DISPLAY is not
the preferable/acceptable solution, as it simply skips the failing tests.
Check out the build.xml. Several tests are only conditionally executed,
depending on whether DISPLAY is set:
where property have.display is conditionally set earlier on based on:
I turned to debugging the Junit tests and determined that the following
tests are failing:
This is the maintainer address of Debian's Java team
debian-j...@lists.debian.org for discussions and questions.