I think I've got it working now. See https://travis-ci.org/apache/logging-log4j2/builds/579990414 for the specific run.
On Mon, 2 Sep 2019 at 16:23, Matt Sicker <[email protected]> wrote: > > Ok, I'm getting annoyed from all the build failure emails from Travis. > I'm looking into fixing this now. > > On Thu, 1 Aug 2019 at 13:32, Matt Sicker <[email protected]> wrote: > > > > If their documentation is wrong, there are probably two options: > > > > 1. Run find . in a job and look through the file system. > > 2. Use the apt addon thing to install the package for the specific JDK > > version (how I have my CV set up in Travis for installing TeXLive). > > > > On Thu, Aug 1, 2019 at 10:55, Ralph Goers <[email protected]> > > wrote: > >> > >> Do you know of a way to fine out where they are supposed to be installed? > >> > >> Ralph > >> > >> > On Aug 1, 2019, at 8:51 AM, Matt Sicker <[email protected]> wrote: > >> > > >> > Sounds like they've got a bug in their jdk11 support. At work (well, > >> > to be more specific, on ci.jenkins.io), we've been using separate > >> > agents for jdk8 and jdk11. I haven't seen anyone using Travis in the > >> > Jenkins org that has bothered to set up Java 11. > >> > > >> > On Thu, 1 Aug 2019 at 10:44, Ralph Goers <[email protected]> > >> > wrote: > >> >> > >> >> I tried fixing the travis build but I am at a loss. I have no idea how > >> >> to find out where the various JDKs are installed. When I configure the > >> >> job to use openjdk11 by default it prints out that it is using > >> >> /home/travis/openjsk11. When I put that into the toolchains definition > >> >> the JDK 8 build fails saying it can’t be found. > >> >> > >> >> Help. > >> >> > >> >> Ralph > >> > > >> > > >> > > >> > -- > >> > Matt Sicker <[email protected]> > >> > > >> > >> > > -- > > Matt Sicker <[email protected]> > > > > -- > Matt Sicker <[email protected]> -- Matt Sicker <[email protected]>
