On 2019/03/28 13:51, Kurt Miller wrote: > > > > > > > JDK 11 is the next long term supported JDK so I figured it > would be a good idea to port it to OpenBSD. The port is > working > well enough to build and bootstrap itself, however there are > likely numerous things that don’t work or are buggy. > > The main repo for the bsd-port branch is being hosted by > Greg Lewis here: > > https://github.com/battleblow/openjdk-jdk11u/tree/bsd-port > > And was forked from AdoptOpenJDK’s github mirror of OpenJDK’s > source. AdoptOpenJDK will be handling the LTS for the JDKs so > this is a reasonable setup for keeping 11u up to date with updates. > > The port has been committed and is ready for wider testing. >
So far I have, at least to some extent, tested this with unifi, solr and josm, they are working fine for me. Unifi needed a change because JDK 11 no longer includes javax.activation - it looks possible that elasticsearch and logstash may have a similar issue so those would be good things to test with it. If they do have a problem, the quick fix would be to change MODJAVA_VER from the current 1.8+ to 1.8. The more involved fix would be to fetch the class from elsewhere and figure out how to include it (generally would be easier done upstream than in ports). Most java ports use javaPathHelper to determine which JDK version to use. This normally autodetects based on the dependency recorded in the package database, but for easy comparison you can just set JAVAHOME=/usr/local/jdk-11 or JAVAHOME=/usr/local/jdk-1.8.0 in the environment.
