Re: [apache/commons-lang] LANG-1346: Remove deprecation from RandomStringUtils (f2d8493)

There is no concrete release date yet, but hopefully it should not take to long. Am 17.10.2017 um 04:04 schrieb Daniel Kirkdorffer: When will this be released? - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org

[GitHub] commons-io pull request #48: Add more varied input data to tests in FileSyst...

GitHub user testingsavvy opened a pull request: https://github.com/apache/commons-io/pull/48 Add more varied input data to tests in FileSystemUtilsTestCase This PR adds two test cases with exercise `FileSystemUtilsTestCase#freeSpaceWindows` with one larger amount of free disk

Do we really need to read keepalive NOOP responses from FTP server?

Hi. I'm using FTPClient.retrieveFileStream() and therefore I need to implement keepalive mechanism by my own. I wanted to mimic the implementation from FTPClient.CSL, but then I thought: Most FTP servers don't reply to NOOPs until transmission has finished and yet, sending NOOPs helps to keep

[RESULT] Release Compress 1.15 based on RC1

Hi all with +1s by Bruno P. Kinoshita, Gary Gregory, Oliver Heger and my own implicit one the vote has passed. I'll publish the artifacts, give the mirrors some time to catch up and announce the release later today. Thanks to all wh looked into the RC. Stefan

Re: Do we really need to read keepalive NOOP responses from FTP server?

On 17 October 2017 at 12:34, Basin Ilya wrote: > Hi. > I'm using > FTPClient.retrieveFileStream() > > and therefore I need to implement keepalive mechanism by my own. Not necessarily. The FTP server does not need the NOOPs. They are only needed to deal with routers that

Re: Do we really need to read keepalive NOOP responses from FTP server?

Hi sebb > No, because some FTP servers *do* support asynchronous control channels. Do you know any? On 17.10.2017 17:54, sebb wrote: > On 17 October 2017 at 12:34, Basin Ilya wrote: >> Hi. >> I'm using >> FTPClient.retrieveFileStream() >> >> and therefore I need to

Re: Do we really need to read keepalive NOOP responses from FTP server?

On 17 October 2017 at 16:01, Basin Ilya wrote: > Hi sebb > >> No, because some FTP servers *do* support asynchronous control channels. > Do you know any? I cannot remember the name, but I know I came across at least one when testing. But even if there were currently no such

Re: [ANN] Apache Commons Compress 1.15 Released

Thank you Stefan for shepherding this release. Gary On Tue, Oct 17, 2017 at 11:55 AM, Stefan Bodewig wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > The Apache Commons Team is pleased to announce the release of Apache > Commons Compress 1.15. > > The Apache

Re: [1/2] commons-compress git commit: COMPRESS-423 - Add ZStandard decompression support using Zstd-JNI

Should it be "Z_STANDARD" instead of "ZSTANDARD" since "standard" is a word? Gary On Tue, Oct 17, 2017 at 12:23 PM, wrote: > Repository: commons-compress > Updated Branches: > refs/heads/master 89bc17055 -> 1c382914c > > > COMPRESS-423 - Add ZStandard decompression

[ANN] Apache Commons Compress 1.15 Released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Apache Commons Team is pleased to announce the release of Apache Commons Compress 1.15. The Apache Commons Compress Library defines an API for working with compression and archive formats. These include: bzip2, gzip, pack200, lzma, xz, Snappy,

[lang] Module Info

See latest changes. https://github.com/apache/commons-lang/pull/299/files https://travis-ci.org/apache/commons-lang/builds/289148663 It now builds on Java 7, 8 and 9, varying what it does on each JDK. Releases will need to be on Java 9 for the jar file, but 8 for the site plugin if I

Re: [1/2] commons-compress git commit: COMPRESS-423 - Add ZStandard decompression support using Zstd-JNI

On 2017-10-17, Gary Gregory wrote: > Should it be "Z_STANDARD" instead of "ZSTANDARD" since "standard" is a word? Zstandard seems to be the official captitalization: http://www.zstd.net/ But I should check whether it's been used consistently over the last few commits, I doubt it. Stefan

[VOTE] Release Apache Commons Codec 1.11 from RC1

Hi All, We have fixed quite a few bugs and added some significant enhancements since Apache Commons Codec 1.10 was released, so I would like to release Apache Commons Codec 1.11. Apache Commons Codec 1.11 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/commons/codec

Re: [VOTE] Release Apache Commons IO 2.6 based on RC3

should read "five year old issue..." Am 17.10.2017 um 22:05 schrieb Pascal Schumacher: Seems to be intentional and the case since 2.4. There is already a five year only issue complaining about this: https://issues.apache.org/jira/browse/IO-350 Am 17.10.2017 um 22:01 schrieb Oliver Heger:

Re: [VOTE] Release Apache Commons IO 2.6 based on RC3

Seems to be intentional and the case since 2.4. There is already a five year only issue complaining about this: https://issues.apache.org/jira/browse/IO-350 Am 17.10.2017 um 22:01 schrieb Oliver Heger: Build works fine with Java 1.7 and 1.8 on Windows 10. Artifacts and site look good. There

Re: [VOTE] Release Apache Commons IO 2.6 based on RC3

Build works fine with Java 1.7 and 1.8 on Windows 10. Artifacts and site look good. There is something strange in the OSGi meta data: The Export-Package header obviously lists wrong version numbers for some of the packages. For about half of the packages the version is set to "1.4.", for the

Re: [lang] Module Info

Thanks for the update! With your changes travis now executes "mvnclean install" as the main script. Before it was executing the default goal of the pom ("mvn clean verify apache-rat:check clirr:check checkstyle:check findbugs:check javadoc:javadoc") It would be nice if you could update the

Re: [VOTE] Release Apache Commons Codec 1.11 from RC1

[ X ] +1 Release these artifacts Checked out from tag, confirmed revision is 1812411. Build passing with `mvn clean test site` on Apache Maven 3.3.9 Maven home: /usr/share/maven Java version: 1.8.0_131, vendor: Oracle Corporation Java home: /opt/jdk1.8.0_131/jre Default locale: en_NZ, platform