Configure Travis for Java 11 #870
Assignees
Labels
Comments
jfcabral
added a commit
that referenced
this issue
Jul 21, 2019
* Migrate from Ubuntu 14.04 (trusty) into Ubuntu 16.04 (xenial)
jfcabral
added a commit
that referenced
this issue
Jul 21, 2019
* Disable dokka-maven-plugin in activejdbc-kt as a WA until the plugin supports JDK11
jfcabral
added a commit
that referenced
this issue
Jul 21, 2019
* Add module `java.xml.bind` as added in java9 branch in order to ensure the tests can properly execute
|
@jfcabral please see comment #869 (comment). Basically we need two builds now, one for Java8 and the other for Java11. It would be best to not trigger both if there is a commit on one for the sake of efficiency |
jfcabral
added a commit
that referenced
this issue
Jul 22, 2019
* Migrate from Ubuntu 14.04 (trusty) into Ubuntu 16.04 (xenial) * Setup JDK11 builds
ipolevoy
pushed a commit
that referenced
this issue
Jul 22, 2019
#870 - TravisCI - Configure Travis for Java 11
jfcabral
added a commit
that referenced
this issue
Jul 22, 2019
ipolevoy
pushed a commit
that referenced
this issue
Jul 22, 2019
#870 - TravisCI - Ensure java8 branch is also deployed into maven repo
|
@jfcabral this seems to be done, shall we close it? |
|
Indeed, fine by me 😉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@jfcabral how hard would this be? Also, I presume we will be maintaining v 2.3 with minor releases on Java 8 for existing projects for a while, this means independent builds for Java 8 and 11. We might also create a separate branch Java8 to continue with 2.3.x releases.
Thoughts?
The text was updated successfully, but these errors were encountered: