Re: [all] Linking to sites will break or become misleading overtime.

I just noticed that all sites have been archived for our Commons CSV: https://commons.apache.org/proper/commons-csv/ I love that! Gary On Wed, Jul 19, 2017 at 8:26 AM, Gary Gregory wrote: > I tried one approach for Commons Codec: > > https://commons.apache.org/proper/commons-codec/ > > See the

Re: [VOTE] Release Apache Commons DbUtils 1.7 based on RC2

This vote passes with the following result: - Gary Gregory: +1 (binding) - Oliver Heger: +1 (binding) - Rob Tompkins: +1 (binding) - Amey Jadiye: +1 (non-binding) Thank you to all who helped make this release and for reviewing the RCs! I’ll work on publishing everything soon. On Tue, Jul 18, 20

[GitHub] commons-imaging pull request #29: Improve various unit tests style

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

Re: [email] Preparing Commons Email Release 1.5 ...

Go for it! :-) Gary On Thu, Jul 20, 2017 at 12:58 PM, Siegfried Goeschl wrote: > Hi folks, > > I think is is time to get a commons-email-1.5 out of the door - any > objection to start a release > > Thanks in advance, > > Siegfried Goeschl > > > --

Fwd: svn commit: r1802527 - /commons/proper/email/trunk/RELEASE-NOTES.txt

Note that the current version of javax.mail is 1.6.0 and requires Java 7 IIRC. Gary -- Forwarded message -- From: Date: Thu, Jul 20, 2017 at 12:34 PM Subject: svn commit: r1802527 - /commons/proper/email/trunk/RELEASE-NOTES.txt To: comm...@commons.apache.org Author: sgoeschl Da

[email] Preparing Commons Email Release 1.5 ...

Hi folks, I think is is time to get a commons-email-1.5 out of the door - any objection to start a release Thanks in advance, Siegfried Goeschl - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional comma

[GitHub] commons-text pull request #56: add-some-Unit Tests

Github user PascalSchumacher commented on a diff in the pull request: https://github.com/apache/commons-text/pull/56#discussion_r128594766 --- Diff: src/test/java/org/apache/commons/text/ExtendedMessageFormatTest.java --- @@ -416,6 +416,81 @@ public void testSetFormatsByArgumentInd

[GitHub] commons-text pull request #56: add-some-Unit Tests

Github user PascalSchumacher commented on a diff in the pull request: https://github.com/apache/commons-text/pull/56#discussion_r128595088 --- Diff: src/test/java/org/apache/commons/text/ExtendedMessageFormatTest.java --- @@ -416,6 +416,81 @@ public void testSetFormatsByArgumentInd

[GitHub] commons-text pull request #56: add-some-Unit Tests

Github user PascalSchumacher commented on a diff in the pull request: https://github.com/apache/commons-text/pull/56#discussion_r128595517 --- Diff: src/test/java/org/apache/commons/text/ExtendedMessageFormatTest.java --- @@ -416,6 +416,81 @@ public void testSetFormatsByArgumentInd

Re: [vfs] Lcurly=no (was: svn commit: r1802440 - /commons/proper/vfs/trunk/core/src/test/java/org/apache/commons/vfs2/provider/jar/test/JarAttributesTestCase.java

Sure, that sounds good, EOL on lcurl. On Jul 20, 2017 01:08, "Bernd Eckenfels" wrote: > Hello Gary, > > Well I don't remember that we agreed on it, however as I said both is > fine. Should we then make the change to checkstyle file and if yes, what > change? Using eol for all lcurly entries? > >

Re: [vfs] Lcurly=no (was: svn commit: r1802440 - /commons/proper/vfs/trunk/core/src/test/java/org/apache/commons/vfs2/provider/jar/test/JarAttributesTestCase.java

Hello Gary, Well I don't remember that we agreed on it, however as I said both is fine. Should we then make the change to checkstyle file and if yes, what change? Using eol for all lcurly entries? Gruss Bernd Gruss Bernd -- http://bernd.eckenfels.net From: Gary