[GitHub] commons-compress issue #37: COMPRESS-410 - cherry picked to fix merging issu...

2017-06-18 Thread coveralls
Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/37 [![Coverage Status](https://:/builds/12024033/badge)](https://:/builds/12024033) Coverage decreased (-0.08%) to 84.652% when pulling

[GitHub] commons-compress issue #37: COMPRESS-410 - cherry picked to fix merging issu...

2017-06-18 Thread sesuncedu
Github user sesuncedu commented on the issue: https://github.com/apache/commons-compress/pull/37 There seems to be something amiss with Hudson (it can't checkout origin/master ... ) --- If your project is set up for it, you can reply to this email and have your reply appear on

Build failed in Jenkins: Commons-Compress PullRequest Builder #29

2017-06-18 Thread Apache Jenkins Server
See -- GitHub pull request #37 to apache/commons-compress [EnvInject] - Loading node environment variables. Building remotely on H14 (ubuntu xenial) in workspace

Build failed in Jenkins: Commons-Compress PullRequest Builder #28

2017-06-18 Thread Apache Jenkins Server
See -- GitHub pull request #37 to apache/commons-compress [EnvInject] - Loading node environment variables. Building remotely on H14 (ubuntu xenial) in workspace

[GitHub] commons-compress pull request #37: COMPRESS-410 - cherry picked to fix mergi...

2017-06-18 Thread sesuncedu
GitHub user sesuncedu opened a pull request: https://github.com/apache/commons-compress/pull/37 COMPRESS-410 - cherry picked to fix merging issues Remove non-NIO character set encoders. Fixes rebasing related issues in previous PR You can merge this pull request into a

Build failed in Jenkins: Commons-Compress PullRequest Builder #27

2017-06-18 Thread Apache Jenkins Server
See -- GitHub pull request #37 to apache/commons-compress [EnvInject] - Loading node environment variables. Building remotely on H14 (ubuntu xenial) in workspace

[GitHub] commons-compress pull request #36: COMPRESS-410 Remove Non-NIO character set...

2017-06-18 Thread sesuncedu
Github user sesuncedu closed the pull request at: https://github.com/apache/commons-compress/pull/36 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[OT][ALL] "Speeding up" T-CI builds

2017-06-18 Thread Gary Gregory
Since we are looking more and more into Travis, I posting this for those interested: https://docs.travis-ci.com/user/speeding-up-the-build/ Gary

Build failed in Jenkins: Commons-Compress PullRequest Builder #26

2017-06-18 Thread Apache Jenkins Server
See -- GitHub pull request #36 to apache/commons-compress [EnvInject] - Loading node environment variables. Building remotely on H14 (ubuntu xenial) in workspace

Jenkins build is back to stable : Commons-Compress PullRequest Builder ยป Apache Commons Compress #24

2017-06-18 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional

Jenkins build is back to stable : Commons-Compress PullRequest Builder #24

2017-06-18 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail:

Build failed in Jenkins: Commons-Compress PullRequest Builder #25

2017-06-18 Thread Apache Jenkins Server
See -- GitHub pull request #36 to apache/commons-compress [EnvInject] - Loading node environment variables. Building remotely on H14 (ubuntu xenial) in workspace

[GitHub] commons-cli issue #14: Added BugCLI260 JUnit Test

2017-06-18 Thread jlm429
Github user jlm429 commented on the issue: https://github.com/apache/commons-cli/pull/14 Yep, that works for me. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and

[GitHub] commons-cli issue #14: Added BugCLI260 JUnit Test

2017-06-18 Thread jlm429
Github user jlm429 commented on the issue: https://github.com/apache/commons-cli/pull/14 Yep, that works for me. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and

[GitHub] commons-fileupload issue #7: FILEUPLOAD-238: add tests for the portlet packa...

2017-06-18 Thread kinow
Github user kinow commented on the issue: https://github.com/apache/commons-fileupload/pull/7 I use pull requests when I want someone else to review my code. In this case, I modified the tests design a wee bit too (not just added portlet tests), so would like that someone confirmed

Re: Wondering VFS will support Read/Write on Google Cloud Storage?

2017-06-18 Thread Bernd
Thanks for the try. This is pretty strange since your mount path looks simple and VFS file: provider is not doing much besides using normal Java API to access the filesystem. so this looks more like a Java/fuse/gcs-fuse problem. Can you try File f = new File("/tmp/gcs"); Systen,out.println("f

[GitHub] commons-fileupload issue #1: Commons fileupload headerfix

2017-06-18 Thread jochenw
Github user jochenw commented on the issue: https://github.com/apache/commons-fileupload/pull/1 On another issue: Please remove .classpath, and .project from the pull request. These are IDE specific, thus not supposed to live in an Apache project. --- If your project is set up for

[GitHub] commons-fileupload issue #1: Commons fileupload headerfix

2017-06-18 Thread jochenw
Github user jochenw commented on the issue: https://github.com/apache/commons-fileupload/pull/1 Honestly: 88 files changed for one pull request? No chance to get that pulled in. Try to split your changes into smaller change sets. --- If your project is set up for it, you can reply

[GitHub] commons-fileupload issue #7: FILEUPLOAD-238: add tests for the portlet packa...

2017-06-18 Thread jochenw
Github user jochenw commented on the issue: https://github.com/apache/commons-fileupload/pull/7 Bruno, you are a Commons PMC member. Why use a Github pull request, and not just do a commit? --- If your project is set up for it, you can reply to this email and have your reply appear

[GitHub] commons-cli issue #14: Added BugCLI260 JUnit Test

2017-06-18 Thread chtompki
Github user chtompki commented on the issue: https://github.com/apache/commons-cli/pull/14 No worries at all. While here, what are your thoughts about that scenario? To me it seems odd if you concatenated a flag with the value it represents. Clearly Java delimits arguments passed

[GitHub] commons-cli issue #14: Added BugCLI260 JUnit Test

2017-06-18 Thread chtompki
Github user chtompki commented on the issue: https://github.com/apache/commons-cli/pull/14 No worries at all. While here, what are your thoughts about that scenario? To me it seems odd if you concatenated a flag with the value it represents. Clearly Java delimits arguments passed

[GitHub] commons-cli issue #14: Added BugCLI260 JUnit Test

2017-06-18 Thread jlm429
Github user jlm429 commented on the issue: https://github.com/apache/commons-cli/pull/14 my bad... I guess it makes sense to wait to merge the test until the bug is fixed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] commons-cli issue #14: Added BugCLI260 JUnit Test

2017-06-18 Thread jlm429
Github user jlm429 commented on the issue: https://github.com/apache/commons-cli/pull/14 my bad... I guess it makes sense to wait to merge the test until the bug is fixed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] commons-text issue #46: TEXT-85:Added CaseUtils class with camel case conver...

2017-06-18 Thread chtompki
Github user chtompki commented on the issue: https://github.com/apache/commons-text/pull/46 Will try to get to this today. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[GitHub] commons-cli issue #14: Added BugCLI260 JUnit Test

2017-06-18 Thread chtompki
Github user chtompki commented on the issue: https://github.com/apache/commons-cli/pull/14 My impression base on my reading of the [CLI-260](https://issues.apache.org/jira/browse/CLI-260) is that from this code: ```java private DefaultParser parser; private

[GitHub] commons-cli issue #14: Added BugCLI260 JUnit Test

2017-06-18 Thread chtompki
Github user chtompki commented on the issue: https://github.com/apache/commons-cli/pull/14 My impression base on my reading of the [CLI-260](https://issues.apache.org/jira/browse/CLI-260) is that from this code: ```java private DefaultParser parser; private

[GitHub] commons-text pull request #51: TEXT-91: RandomStringGenerator should be able...

2017-06-18 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/commons-text/pull/51 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] commons-text pull request #53: revert "Added IBM Jdk8 build support to travi...

2017-06-18 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/commons-text/pull/53 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] commons-text issue #53: revert "Added IBM Jdk8 build support to travis-ci co...

2017-06-18 Thread coveralls
Github user coveralls commented on the issue: https://github.com/apache/commons-text/pull/53 [![Coverage Status](https://:/builds/12019073/badge)](https://:/builds/12019073) Changes Unknown when pulling **e100a60844841400d9191f5788536c68a3427900 on

[GitHub] commons-text pull request #53: revert "Added IBM Jdk8 build support to travi...

2017-06-18 Thread PascalSchumacher
GitHub user PascalSchumacher opened a pull request: https://github.com/apache/commons-text/pull/53 revert "Added IBM Jdk8 build support to travis-ci configuration" The build fails, but this failure is not reflected in the travis build status. Code-coverage is broken. You can merge

[GitHub] commons-text issue #52: Test: Improved testcase coverage for StrBuilder

2017-06-18 Thread PascalSchumacher
Github user PascalSchumacher commented on the issue: https://github.com/apache/commons-text/pull/52 Thanks! Please separate the formatting fixes and the test additions into different commits. Please stick to the existing code style for the new tests (no new line at