[
https://issues.apache.org/jira/browse/COMPRESS-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073530#comment-16073530
]
ASF GitHub Bot commented on COMPRESS-413:
-----------------------------------------
GitHub user sesuncedu opened a pull request:
https://github.com/apache/commons-compress/pull/49
COMPRESS-413 set execute back on mvnw
mvnw seems to have lost it's execute mode bits.
Merge asap
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sesuncedu/commons-compress COMPRESS-413-chmod
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/commons-compress/pull/49.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #49
----
commit 37d6151d325017de84d034b773a78e78c2ba8d37
Author: Simon Spero <sesunc...@gmail.com>
Date: 2017-07-04T11:59:30Z
set execute back on mvnw
----
> 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)
