commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Spero (JIRA)" <>
Subject [jira] [Commented] (COMPRESS-413) Travis build redundantly repeats compilation and tests redundantly
Date Fri, 30 Jun 2017 22:09:00 GMT


Simon Spero commented on COMPRESS-413:

Oracle JDK 7 is EOL and is missing critical security patches.  OpenJDK  7
is at least lightly patched.

Oracle JDK and OpenJDK are in a different situation to IBM java.
Open/Oracle JDKs both use the same virtual machine, and the roughly the
same source trees, whereas IBM java uses a completely different VM
implementation (J9), and also has a few differences in the runtime
libraries (mostly openjdk, but there are a few differences).  Any code that
uses private interfaces not covered by the TCK is having problems.

I haven't had any

On Fri, Jun 30, 2017 at 5:23 PM, ASF GitHub Bot (JIRA) <>

> Travis build redundantly repeats compilation and tests redundantly
> ------------------------------------------------------------------
>                 Key: COMPRESS-413
>                 URL:
>             Project: Commons Compress
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 1.14
>         Environment: Travis
>            Reporter: Simon Spero
>            Priority: Minor
>              Labels: CI
>             Fix For: 1.15
>   Original Estimate: 0h
>  Remaining Estimate: 0h
> The Travis build setup is suboptimal.
> At the moment, code is compiled and installed by the default install phase.  
> Then the default build phase is executed, which compiles and runs the tests.
> If the tests succeed, then the build is cleaned, recompiled, and retested; this time
> coverage enabled. 
> The .travis.yml file could be changed to skip the install phase, and to run tests with
coverage during the build phase. 
> The coveralls plugin can be configured in the pom  to not fail the build if the service
is unreachable, so forks that don't have jacoco enabled won't always have their builds fail.

> Also, the jdk switching in the trusty container seems to be not working properly at the
moment, so installing a jdk7 doesn't work properly.
> These changes evolved as I was poking jenkins last night.

This message was sent by Atlassian JIRA

View raw message