Simple Maven example fails with unusual error

[Mark Raynsford]

On 2018-07-23T17:22:34 +0200
Johan Vos <johan.vos at gluonhq.com> wrote:

> Hi Mark,
> 
> So it seems these issues are not OpenJFX specific, and more projects will
> run into this?
> I'm a bit worried about the grey zone between OpenJDK and Maven/Gradle...
> @Kevin are you aware of someone from the jigsaw team who is working in this
> zone? Alan Bateman?

Depends on which of the two errors you're referring to. The one
regarding the version number is not strictly OpenJFX specific, it's
just that OpenJFX happened to pick a version number format that the JVM
doesn't like.

The issue relating to the compiler raising an
IllegalArgumentException... I have no idea who's fault that is. I've
been working with a lot of modular projects for over a year and only
saw anything similar to this error when working with old versions of
the compiler plugin (and those were fixed). Those issues were strictly
down to an embedded version of ASM (pre 6.1) that didn't support the
newer bytecode format. None of the ~70 or so modular projects I
currently compile have this problem (both projects that are themselves
modular, and have dependencies on the module path).

I'm a little mystified as to why it's shown up today at all, given that
it didn't when I initially posted to the list. I can reproduce the
issue on Travis CI:

  https://travis-ci.org/io7m/javafx-example-20180721/builds/407068017

... so it doesn't appear to be my environment that's broken (or at
least it's not *just* mine!)

-- 
Mark Raynsford | http://www.io7m.com