Re: [VOTE] Release Commons Codec 1.8-RC4

2013-04-21 Thread Gary Gregory
Yes, the proposed solution did not fit in the BaseN framework IIRC. So
we need to talk about whether B32 and B64 need to keep common code or
whether both should be optimized in separate code bases.

Gary

On Apr 21, 2013, at 0:36, Henri Yandell flame...@gmail.com wrote:

 I assume https://issues.apache.org/jira/browse/CODEC-166 is moving to a
 target of 1.9?


 On Sat, Apr 20, 2013 at 1:29 PM, Bruno P. Kinoshita 
 brunodepau...@yahoo.com.br wrote:

 +1 (non-binding), all looks good.

 Apache Maven 3.0.4
 Java 1.7.0_09
 Debian 3.2.0-4-amd64

 Cheers,

 Bruno P. Kinoshita
 http://kinoshita.eti.br
 http://tupilabs.com


 --- Em sex, 19/4/13, Gary Gregory ggreg...@apache.org escreveu:

 De: Gary Gregory ggreg...@apache.org
 Assunto: [VOTE] Release Commons Codec 1.8-RC4
 Para: Commons Developers List dev@commons.apache.org
 Data: Sexta-feira, 19 de Abril de 2013, 13:56
 Hello All:

 This is a VOTE to release Commons Codec 1.8-RC4.

 Commons Codec 1.8 requires a minimum of Java 1.6

 Changes from 1.8-RC3 are:

 Add pmd.xml to source distribution to build the site.

 Changes from 1.8-RC2 are:

 Clarify NOTICE.txt

 Changes from 1.8-RC1 are:

 o Set the correct version for the Ant build in
 default.properties
 o Fix URLs in NOTICE.txt file and Java source for ASpell.

 Changes in this version include:

 New features:
 o CODEC-168:  Add
 DigestUtils.updateDigest(MessageDigest, InputStream).
 Thanks to Daniel Cassidy.
 o CODEC-167:  Add JUnit to test our decode with pad
 character in the middle.
 o CODEC-161:  Add Match Rating Approach (MRA) phonetic
 algorithm encoder.
 Thanks to crice.

 Fixed Bugs:
 o CODEC-163:  ColognePhonetic encoder unnecessarily
 creates many char
 arrays on every loop run. Thanks to leo141.
 o CODEC-160:  Base64.encodeBase64URLSafeString doesn't
 add padding
 characters at the end.

 This VOTE is open for at least 72 hours until April 22 2013
 at 1:00 PM EST.

 The files:

 https://repository.apache.org/content/repositories/orgapachecommons-121/

 The tag:

 https://svn.apache.org/repos/asf/commons/proper/codec/tags/1.8-RC4

 The site:

 https://people.apache.org/~ggregory/commons-codec/1.8-RC4/site/

 Thank you,
 Gary Gregory
 --
 E-Mail: garydgreg...@gmail.com
 | ggreg...@apache.org
 Java Persistence with Hibernate, Second Edition
 http://www.manning.com/bauer3/
 JUnit in Action, Second Edition http://www.manning.com/tahchiev/
 Spring Batch in Action http://www.manning.com/templier/
 Blog: http://garygregory.wordpress.com
 Home: http://garygregory.com/
 Tweet! http://twitter.com/GaryGregory

 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [io] readying release?

2013-04-21 Thread Gary Gregory
My view is that we do not have to fix or address everything in each
release that is outstanding. In my mind its important to keep the
release trains moving.

Gary

On Apr 21, 2013, at 0:45, Henri Yandell flame...@gmail.com wrote:

 Because they're low hanging fruit:

 Javadoc: https://issues.apache.org/jira/browse/IO-299
 Javadoc: https://issues.apache.org/jira/browse/IO-328
 Proposed fix: https://issues.apache.org/jira/browse/IO-295

 Agreed on IO-356. Not sure how critical IO-350 is :)



 On Tue, Apr 16, 2013 at 3:15 PM, sebb seb...@gmail.com wrote:

 On 16 April 2013 20:09, Gary Gregory garydgreg...@gmail.com wrote:

 Hi All:

 I'm thinking of a release sooner rather than later. Thoughts?


 I think the following need resolving:

 https://issues.apache.org/jira/browse/IO-350
 https://issues.apache.org/jira/browse/IO-356

 Possibly some others


 Gary

 --
 E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
 Java Persistence with Hibernate, Second Edition
 http://www.manning.com/bauer3/
 JUnit in Action, Second Edition http://www.manning.com/tahchiev/
 Spring Batch in Action http://www.manning.com/templier/
 Blog: http://garygregory.wordpress.com
 Home: http://garygregory.com/
 Tweet! http://twitter.com/GaryGregory



-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons Math 3.2 - RC5

2013-04-21 Thread Luc Maisonobe
Le 21/04/2013 01:24, Emmanuel Bourg a écrit :
 Le 09/04/2013 09:23, Emmanuel Bourg a écrit :
 
 I packaged it last week, it's in the new package queue and
 should appear in the Debian repository soon.
 
 The package is now available in the experimental repository:
 
 http://packages.qa.debian.org/c/commons-math3.html

Thanks Emmanuel.

Luc

 
 
 Emmanuel Bourg
 
 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [io] readying release?

2013-04-21 Thread Benedikt Ritter
I agree. I think it is vital that people have the feeling that something is
happening (without following the Dev ML). This works best by pushing out
releases frequently.


2013/4/21 Gary Gregory garydgreg...@gmail.com

 My view is that we do not have to fix or address everything in each
 release that is outstanding. In my mind its important to keep the
 release trains moving.

 Gary

 On Apr 21, 2013, at 0:45, Henri Yandell flame...@gmail.com wrote:

  Because they're low hanging fruit:
 
  Javadoc: https://issues.apache.org/jira/browse/IO-299
  Javadoc: https://issues.apache.org/jira/browse/IO-328
  Proposed fix: https://issues.apache.org/jira/browse/IO-295
 
  Agreed on IO-356. Not sure how critical IO-350 is :)
 
 
 
  On Tue, Apr 16, 2013 at 3:15 PM, sebb seb...@gmail.com wrote:
 
  On 16 April 2013 20:09, Gary Gregory garydgreg...@gmail.com wrote:
 
  Hi All:
 
  I'm thinking of a release sooner rather than later. Thoughts?
 
 
  I think the following need resolving:
 
  https://issues.apache.org/jira/browse/IO-350
  https://issues.apache.org/jira/browse/IO-356
 
  Possibly some others
 
 
  Gary
 
  --
  E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
  Java Persistence with Hibernate, Second Edition
  http://www.manning.com/bauer3/
  JUnit in Action, Second Edition http://www.manning.com/tahchiev/
  Spring Batch in Action http://www.manning.com/templier/
  Blog: http://garygregory.wordpress.com
  Home: http://garygregory.com/
  Tweet! http://twitter.com/GaryGregory
 
 

 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org




-- 
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter


[continuum] BUILD FAILURE: Apache Commons - Commons IO -

2013-04-21 Thread Continuum@vmbuild
  Build using Java 1.6
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Continuum-Build-Host: vmbuild
X-Continuum-Project-Id: 83
X-Continuum-Project-Name: Commons IO

Online report : 
http://vmbuild.apache.org/continuum/buildResult.action?buildId=26775projectId=83

Build statistics:
  State: Failed
  Previous State: Ok
  Started at: Sun 21 Apr 2013 12:20:09 +
  Finished at: Sun 21 Apr 2013 12:22:04 +
  Total time: 1m 54s
  Build Trigger: Schedule
  Build Number: 334
  Exit code: 1
  Building machine hostname: vmbuild
  Operating system : Linux(unknown)
  Java Home version : 
  java version 1.6.0_30
  Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
  Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)

  Builder version :
  Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+)
  Java version: 1.6.0_30
  Java home: /usr/lib/jvm/jdk1.6.0_30/jre
  Default locale: en_AU, platform encoding: UTF-8
  OS name: linux version: 2.6.32-41-server arch: amd64 Family: 
unix


SCM Changes:

Changed: sebb @ Sun 21 Apr 2013 11:50:07 +
Comment: Not all charsets support encoding; fix up ignored test so it no longer 
fails
Files changed:
  
/commons/proper/io/trunk/src/test/java/org/apache/commons/io/input/CharSequenceInputStreamTest.java
 ( 1470288 )


Dependencies Changes:

No dependencies changed



Build Definition:

POM filename: pom.xml
Goals: clean deploy   
Arguments: --batch-mode -Pjava-1.6 -Dgpg.skip -Prelease
Build Fresh: false
Always Build: false
Default Build Definition: true
Schedule: COMMONS_SCHEDULE
Profile Name: Maven 2.2.1
Description: Build using Java 1.6


Test Summary:

Tests: 1021
Failures: 0
Errors: 1
Success Rate: 99
Total time: 75.52698




-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [io] readying release?

2013-04-21 Thread sebb
On 21 April 2013 05:44, Henri Yandell flame...@gmail.com wrote:

 Because they're low hanging fruit:

 Javadoc: https://issues.apache.org/jira/browse/IO-299
 Javadoc: https://issues.apache.org/jira/browse/IO-328


I can do those; partly I was waiting for some feedback, which I now have.


 Proposed fix: https://issues.apache.org/jira/browse/IO-295


I did wonder about using Reflection to solve the issue for Java 7.

Should we still use the command shell for Java 6?


 Agreed on IO-356. Not sure how critical IO-350 is :)



 On Tue, Apr 16, 2013 at 3:15 PM, sebb seb...@gmail.com wrote:

  On 16 April 2013 20:09, Gary Gregory garydgreg...@gmail.com wrote:
 
   Hi All:
  
   I'm thinking of a release sooner rather than later. Thoughts?
  
 
  I think the following need resolving:
 
  https://issues.apache.org/jira/browse/IO-350
  https://issues.apache.org/jira/browse/IO-356
 
  Possibly some others
 
 
  Gary
  
   --
   E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
   Java Persistence with Hibernate, Second Edition
   http://www.manning.com/bauer3/
   JUnit in Action, Second Edition http://www.manning.com/tahchiev/
   Spring Batch in Action http://www.manning.com/templier/
   Blog: http://garygregory.wordpress.com
   Home: http://garygregory.com/
   Tweet! http://twitter.com/GaryGregory
  
 



Re: svn commit: r1470311 - /commons/proper/collections/trunk/src/main/java/org/apache/commons/collections4/MapUtils.java

2013-04-21 Thread sebb
On 21 April 2013 16:21, t...@apache.org wrote:

 Author: tn
 Date: Sun Apr 21 15:21:45 2013
 New Revision: 1470311

 URL: http://svn.apache.org/r1470311
 Log:
 Suppress deprecation warnings for ArrayStack usage.


Surely the code should use whatever the replacement is?


 Modified:

 commons/proper/collections/trunk/src/main/java/org/apache/commons/collections4/MapUtils.java

 Modified:
 commons/proper/collections/trunk/src/main/java/org/apache/commons/collections4/MapUtils.java
 URL:
 http://svn.apache.org/viewvc/commons/proper/collections/trunk/src/main/java/org/apache/commons/collections4/MapUtils.java?rev=1470311r1=1470310r2=1470311view=diff

 ==
 ---
 commons/proper/collections/trunk/src/main/java/org/apache/commons/collections4/MapUtils.java
 (original)
 +++
 commons/proper/collections/trunk/src/main/java/org/apache/commons/collections4/MapUtils.java
 Sun Apr 21 15:21:45 2013
 @@ -910,6 +910,7 @@ public class MapUtils {
   *  If codenull/code, the text 'null' is output.
   * @throws NullPointerException if the stream is codenull/code
   */
 +@SuppressWarnings(deprecation)
  public static void verbosePrint(final PrintStream out, final Object
 label, final Map?, ? map) {
  verbosePrintInternal(out, label, map, new ArrayStackMap?,
 ?(), false);
  }
 @@ -932,6 +933,7 @@ public class MapUtils {
   *   If codenull/code, the text 'null' is output.
   * @throws NullPointerException if the stream is codenull/code
   */
 +@SuppressWarnings(deprecation)
  public static void debugPrint(final PrintStream out, final Object
 label, final Map?, ? map) {
  verbosePrintInternal(out, label, map, new ArrayStackMap?,
 ?(), true);
  }
 @@ -961,6 +963,7 @@ public class MapUtils {
   * @param debug  flag indicating whether type names should be output.
   * @throws NullPointerException if the stream is codenull/code
   */
 +@SuppressWarnings(deprecation)
  private static void verbosePrintInternal(final PrintStream out, final
 Object label, final Map?, ? map,
   final ArrayStackMap?, ?
 lineage, final boolean debug) {
  printIndent(out, lineage.size());





Re: svn commit: r1470311 - /commons/proper/collections/trunk/src/main/java/org/apache/commons/collections4/MapUtils.java

2013-04-21 Thread Thomas Neidhart
On 04/21/2013 09:20 PM, sebb wrote:
 On 21 April 2013 16:21, t...@apache.org wrote:
 
 Author: tn
 Date: Sun Apr 21 15:21:45 2013
 New Revision: 1470311

 URL: http://svn.apache.org/r1470311
 Log:
 Suppress deprecation warnings for ArrayStack usage.


 Surely the code should use whatever the replacement is?

I deprecated ArrayStack as it is obsoleted by the Deque interface of
Java 6. As we still target Java 5 for collections, I decided to keep it,
as there is no other non-synchronized LIFO stack available (unless you
use a plain LinkedList).

But we could also decide to target Java 6 for collections 4?

Thomas

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: svn commit: r1470311 - /commons/proper/collections/trunk/src/main/java/org/apache/commons/collections4/MapUtils.java

2013-04-21 Thread sebb
On 21 April 2013 21:30, Thomas Neidhart thomas.neidh...@gmail.com wrote:

 On 04/21/2013 09:20 PM, sebb wrote:
  On 21 April 2013 16:21, t...@apache.org wrote:
 
  Author: tn
  Date: Sun Apr 21 15:21:45 2013
  New Revision: 1470311
 
  URL: http://svn.apache.org/r1470311
  Log:
  Suppress deprecation warnings for ArrayStack usage.
 
 
  Surely the code should use whatever the replacement is?

 I deprecated ArrayStack as it is obsoleted by the Deque interface of
 Java 6. As we still target Java 5 for collections, I decided to keep it,
 as there is no other non-synchronized LIFO stack available (unless you
 use a plain LinkedList).

 But we could also decide to target Java 6 for collections 4?


Would it not be better to leave the deprecation until the code actually
needs Java 6?

There's nothing Java 5 users can do about the deprecation, so it's
currently just noise.

Thomas

 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org




Re: [io] readying release?

2013-04-21 Thread Henri Yandell
+1 :)

Regular cadence is huge.


On Sat, Apr 20, 2013 at 11:57 PM, Gary Gregory garydgreg...@gmail.comwrote:

 My view is that we do not have to fix or address everything in each
 release that is outstanding. In my mind its important to keep the
 release trains moving.

 Gary

 On Apr 21, 2013, at 0:45, Henri Yandell flame...@gmail.com wrote:

  Because they're low hanging fruit:
 
  Javadoc: https://issues.apache.org/jira/browse/IO-299
  Javadoc: https://issues.apache.org/jira/browse/IO-328
  Proposed fix: https://issues.apache.org/jira/browse/IO-295
 
  Agreed on IO-356. Not sure how critical IO-350 is :)
 
 
 
  On Tue, Apr 16, 2013 at 3:15 PM, sebb seb...@gmail.com wrote:
 
  On 16 April 2013 20:09, Gary Gregory garydgreg...@gmail.com wrote:
 
  Hi All:
 
  I'm thinking of a release sooner rather than later. Thoughts?
 
 
  I think the following need resolving:
 
  https://issues.apache.org/jira/browse/IO-350
  https://issues.apache.org/jira/browse/IO-356
 
  Possibly some others
 
 
  Gary
 
  --
  E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
  Java Persistence with Hibernate, Second Edition
  http://www.manning.com/bauer3/
  JUnit in Action, Second Edition http://www.manning.com/tahchiev/
  Spring Batch in Action http://www.manning.com/templier/
  Blog: http://garygregory.wordpress.com
  Home: http://garygregory.com/
  Tweet! http://twitter.com/GaryGregory
 
 

 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org




Re: [io] readying release?

2013-04-21 Thread Henri Yandell
On Sun, Apr 21, 2013 at 5:27 AM, sebb seb...@gmail.com wrote:

 On 21 April 2013 05:44, Henri Yandell flame...@gmail.com wrote:


  Proposed fix: https://issues.apache.org/jira/browse/IO-295
 
 
 I did wonder about using Reflection to solve the issue for Java 7.

 Should we still use the command shell for Java 6?


Doesn't seem necessary - those who want the feature on Windows can move to
Java 7. Seems a bit late to go writing code we could have written 10 years
ago to support the last year or two of usefulness before Java 7 is
everywhere :)

Hen