If it broken by JDK9 or JDK10, it'll be broken in JDK11 :-)
And we could start to be checking out JDK14.
Would it be better to have these builds nightly on Jenkins?
What's your usage model for Travis-CI?
I use it to check branch work on my cloned repo, not on the master repo.
Andy
On 10/07/2019 10:05, Rob Vesse wrote:
Yeah, though as with most past Java versions that doesn't mean people aren't
still using them
Having a wide range of builds helps spot any breaking changes or behavioural
subtleties across JVM versions
Rob
On 08/07/2019, 20:30, "Andy Seaborne" <[email protected]> wrote:
Rob,
Aren't java9 and java10 now end-of-life?
If so - do we need them in the general travis (merely because each adds
15-20 mins).
I use Travis for branch development - we can use Jekins to validate master.
In the same vein - what about a 13 Early Access build on ASF Jenkins?
Andy
On 08/07/2019 10:16, [email protected] wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> rvesse pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/jena.git
>
> commit f0bf5f317e0725fd7b375dfa83859692c79216e6
> Author: Rob Vesse <[email protected]>
> AuthorDate: Mon Apr 29 13:44:15 2019 +0100
>
> Build for wider range of JDKs on Travis
> ---
> .travis.yml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/.travis.yml b/.travis.yml
> index 7b39dcc..6b02e49 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -5,5 +5,8 @@ script: mvn -B clean install
> jdk:
> - openjdk8
> - oraclejdk8
> + - openjdk9
> + - openjdk10
> + - openjdk11
> env:
> - JAVA_OPTS="-Xmx3072M -Xms512M -XX:+UseG1GC"
>
