[GitHub] commons-compress issue #33: add-some-Unit-Tests Added some Unit Tests to inc...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/33 [](https://:/builds/12008449) Coverage increased (+0.3%) to 84.673% when pulling

[GitHub] commons-compress issue #33: add-some-Unit-Tests Added some Unit Tests to inc...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/33 [](https://:/builds/12007847) Coverage increased (+0.5%) to 84.812% when pulling

[GitHub] commons-compress issue #33: add-some-Unit-Tests Added some Unit Tests to inc...

Github user TheRealHaui commented on the issue: https://github.com/apache/commons-compress/pull/33 Link to the pull request: https://github.com/apache/commons-compress/pull/35 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] commons-compress pull request #35: Compress 412

GitHub user TheRealHaui opened a pull request: https://github.com/apache/commons-compress/pull/35 Compress 412 Fixed Jira issue Compress 412: https://issues.apache.org/jira/browse/COMPRESS-412 You can merge this pull request into a Git repository by running: $ git pull

[GitHub] commons-io pull request #37: NOP change

GitHub user mweagle opened a pull request: https://github.com/apache/commons-io/pull/37 NOP change You can merge this pull request into a Git repository by running: $ git pull https://github.com/ShiftLeftSecurity/commons-io pr_noop_test Alternatively you can review and apply

[GitHub] commons-compress issue #33: add-some-Unit-Tests Added some Unit Tests to inc...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/33 [](https://:/builds/12008341) Coverage increased (+0.3%) to 84.673% when pulling

[GitHub] commons-compress issue #33: add-some-Unit-Tests Added some Unit Tests to inc...

Github user TheRealHaui commented on the issue: https://github.com/apache/commons-compress/pull/33 @bodewig Thank you for your kind response! Really appreciate that! Therefore I've made all the changes you requested/proposed. And of course added myself as a

[GitHub] commons-compress issue #33: add-some-Unit-Tests Added some Unit Tests to inc...

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/33 [](https://:/builds/12010056) Coverage increased (+0.4%) to 84.713% when pulling

[GitHub] commons-compress issue #35: Compress 412

Github user coveralls commented on the issue: https://github.com/apache/commons-compress/pull/35 [](https://:/builds/12009215) Coverage increased (+0.2%) to 84.678% when pulling

[GitHub] commons-io pull request #37: NOP change

Github user mweagle closed the pull request at: https://github.com/apache/commons-io/pull/37 --- 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 is

[GitHub] commons-fileupload pull request #7: FILEUPLOAD-238: add tests for the portle...

Github user kinow closed the pull request at: https://github.com/apache/commons-fileupload/pull/7 --- 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

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

GitHub user sesuncedu opened a pull request: https://github.com/apache/commons-compress/pull/36 COMPRESS-410 Remove Non-NIO character set encoders. As a special case, the UTF-8 encoder will replace malformed / unmappable input with '?'. This behavior is required for

[GitHub] commons-fileupload pull request #8: FILEUPLOAD-283: add tests for the portle...

GitHub user kinow opened a pull request: https://github.com/apache/commons-fileupload/pull/8 FILEUPLOAD-283: add tests for the portlet package Initial tests for the portlet package. I believe there have been updates to the portlet specification(s) that have not been applied to

Re: [all] Custom build containers in Travis-CI.

> On Jun 16, 2017, at 5:07 AM, Benedikt Ritter wrote: > > Hi, > >> Am 15.06.2017 um 15:17 schrieb Rob Tompkins : >> >> Hello all, >> >> We’ve started an experiment in [text] in regards to using travis-ci to build >> inside containers (specifically

[GitHub] commons-fileupload pull request #7: FILEUPLOAD-238: add tests for the portle...

GitHub user kinow opened a pull request: https://github.com/apache/commons-fileupload/pull/7 FILEUPLOAD-238: add tests for the portlet package Initial tests for the portlet package. I believe there have been updates to the portlet specification(s) that have not been applied to

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

At first I mount my Google Cloud Storage onto directory /tmp/gcs using `gcsfuse`, then I create a small project: https://github.com/tilumi/apache-vfs-debug for testing it VFS can detect my mounting point or not. the execution log: ``` $ls -al /tmp/gcs total 0 drwxrwxrwx 1 root root 0 Jun 17 00:42

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

Github user developerSid commented on the issue: https://github.com/apache/commons-fileupload/pull/1 Sure I can give that a try. I had forgotten about having actually done this. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

Re: [CLI] Changing the code style

No objection from me. +1 and thanks for taking care of it :) Cheers Bruno From: Benedikt Ritter To: Commons Developers List Sent: Friday, 16 June 2017 8:50 PM Subject: [CLI] Changing the code style Hi, CLI unlike

Re: [Codec] we almost had a release...

Go for it ;-) > Am 15.06.2017 um 21:34 schrieb Gary Gregory : > > ... a couple of months ago. Fits and starts. Is anyone available for spit, > polish, and release? > > Gary - To unsubscribe, e-mail:

[FUNCTOR] Why do we have an API module?

Hi, I’m about to start work on functor. Looking at the project, I wonder why we have a separation bewteen an API module and implementations. This feels like overkill to me for a project like functor. Further more I don’t see other parties extending the stuff in the API module. If nobody

[GitHub] commons-compress pull request #34: COMPRESS-405 : Add javadoc for FixedLengt...

Github user asfgit closed the pull request at: https://github.com/apache/commons-compress/pull/34 --- 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

[CLI] Changing the code style

Hi, CLI unlike other components has a custom code style. While other components pretty much follow the Sun code guidelines, the CLI code base uses a style like the Maven project. For me it’s annoying the switch code style configurations between components. If nobody objects, I’d like to apply

Re: [all] Custom build containers in Travis-CI.

Hi, > Am 15.06.2017 um 15:17 schrieb Rob Tompkins : > > Hello all, > > We’ve started an experiment in [text] in regards to using travis-ci to build > inside containers (specifically ibmjava at this point). It seems that it’s a > non-standard practice with regards to

Re: [FUNCTOR] Why do we have an API module?

No objection here too. I've been gathering some links about other libraries and extensions to Java 8, to have a look at functor in the future and see if it would be interesting to have something there, unless it made more sense to put it on lang. The reason for the API module, if memory

Re: [CLI] Changing the code style

+1, keeping same discipline throughout components is always better, I liked the way Lang and Text is maintained at this point. not only checkstyle but findbug, clirr, javadoc also should passed clean for each component. Regards, Amey On Fri, Jun 16, 2017 at 2:20 PM, Benedikt Ritter

Re: [all] Custom build containers in Travis-CI.

> Am 16.06.2017 um 11:07 schrieb Benedikt Ritter : > > Hi, > >> Am 15.06.2017 um 15:17 schrieb Rob Tompkins : >> >> Hello all, >> >> We’ve started an experiment in [text] in regards to using travis-ci to build >> inside containers (specifically ibmjava

[GitHub] commons-text issue #44: [TEXT-80]: Fixed confusing StrLookup API

Github user ameyjadiye commented on the issue: https://github.com/apache/commons-text/pull/44 Lets park this for 2.X release. --- 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

Re: [FUNCTOR] Why do we have an API module?

Yes, the point of the API module was to define the functional interfaces separately from the utility code around them; particularly pre-Java 8, these could be used apart from the utility code from the core. Matt On Jun 16, 2017 4:27 AM, "Bruno P. Kinoshita"

JDK 9 EA Build 174 & JDK 8u152 b04 are available on jdk.java.net

Hi Benedikt, * * *JDK 9 Early Access* build 174 is available at : - jdk.java.net/9/ A summary of all the changes in this build are listed here . Changes which were introduced since the last availability email that may be of