[
https://issues.apache.org/jira/browse/COMPRESS-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073883#comment-16073883
]
ASF GitHub Bot commented on COMPRESS-413:
-----------------------------------------
Github user sesuncedu commented on the issue:
https://github.com/apache/commons-compress/pull/49
Did you also re-add .mvn?
On Jul 4, 2017 8:31 AM, "Stefan Bodewig" <notificati...@github.com> wrote:
> I've made mvnw executable again with eef4e3c
>
<https://github.com/apache/commons-compress/commit/eef4e3c6abac2cc56187877fe2dd5d35fadb6fde>
> but didn't want to mix it with the unrelated changes
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
>
<https://github.com/apache/commons-compress/pull/49#issuecomment-312866129>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/AAZIGwGJNbd4bCXUYGl5JyZIjPEYz8Jtks5sKjCvgaJpZM4ONQ30>
> .
>
> Travis build redundantly repeats compilation and tests redundantly
> ------------------------------------------------------------------
>
> Key: COMPRESS-413
> URL: https://issues.apache.org/jira/browse/COMPRESS-413
> 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 with
> 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
(v6.4.14#64029)
