Re: [Math] LeastSquaresOptimizer Design

2015-09-21 Thread Ole Ersoy
Hola, On 09/21/2015 04:15 PM, Gilles wrote: Hi. On Sun, 20 Sep 2015 15:04:08 -0500, Ole Ersoy wrote: On 09/20/2015 05:51 AM, Gilles wrote: On Sun, 20 Sep 2015 01:12:49 -0500, Ole Ersoy wrote: Wanted to float some ideas for the LeastSquaresOptimizer (Possibly General Optimizer) design. For e

Re: Version number for next commons-io

2015-09-21 Thread Jörg Schaible
sebb wrote: > On 21 September 2015 at 20:03, Phil Steitz wrote: >> On 9/21/15 10:59 AM, sebb wrote: >>> On 21 September 2015 at 18:36, Jörg Schaible >>> wrote: Gary Gregory wrote: > Alternative to keep 100% BC > > - Remove the new method, release 2.5, and add it back for SN

Re: [Math] LeastSquaresOptimizer Design

2015-09-21 Thread Gilles
Hi. On Sun, 20 Sep 2015 15:04:08 -0500, Ole Ersoy wrote: On 09/20/2015 05:51 AM, Gilles wrote: On Sun, 20 Sep 2015 01:12:49 -0500, Ole Ersoy wrote: Wanted to float some ideas for the LeastSquaresOptimizer (Possibly General Optimizer) design. For example with the LevenbergMarquardtOptimizer we

Re: Version number for next commons-io

2015-09-21 Thread sebb
On 21 September 2015 at 20:03, Phil Steitz wrote: > On 9/21/15 10:59 AM, sebb wrote: >> On 21 September 2015 at 18:36, Jörg Schaible wrote: >>> Gary Gregory wrote: >>> Alternative to keep 100% BC - Remove the new method, release 2.5, and add it back for SNAPSHOT - Add the new

Re: Version number for next commons-io

2015-09-21 Thread Phil Steitz
On 9/21/15 10:36 AM, Jörg Schaible wrote: > Gary Gregory wrote: > >> Alternative to keep 100% BC >> >> - Remove the new method, release 2.5, and add it back for SNAPSHOT >> - Add the new method in a new sub-interface > or catch and ignore this special RTE when calling the new method form our > cod

Re: Version number for next commons-io

2015-09-21 Thread Phil Steitz
On 9/21/15 10:59 AM, sebb wrote: > On 21 September 2015 at 18:36, Jörg Schaible wrote: >> Gary Gregory wrote: >> >>> Alternative to keep 100% BC >>> >>> - Remove the new method, release 2.5, and add it back for SNAPSHOT >>> - Add the new method in a new sub-interface >> or catch and ignore this sp

Re: Version number for next commons-io

2015-09-21 Thread sebb
On 21 September 2015 at 18:36, Jörg Schaible wrote: > Gary Gregory wrote: > >> Alternative to keep 100% BC >> >> - Remove the new method, release 2.5, and add it back for SNAPSHOT >> - Add the new method in a new sub-interface > > or catch and ignore this special RTE when calling the new method fo

Re: Version number for next commons-io

2015-09-21 Thread Jörg Schaible
Gary Gregory wrote: > Alternative to keep 100% BC > > - Remove the new method, release 2.5, and add it back for SNAPSHOT > - Add the new method in a new sub-interface or catch and ignore this special RTE when calling the new method form our code. Old clients never asked for it, new/updated clie

Re: Version number for next commons-io

2015-09-21 Thread Gary Gregory
Alternative to keep 100% BC - Remove the new method, release 2.5, and add it back for SNAPSHOT - Add the new method in a new sub-interface Gary On Mon, Sep 21, 2015 at 10:23 AM, Phil Steitz wrote: > On 9/19/15 9:55 AM, sebb wrote: > > On 19 September 2015 at 17:26, Kristian Rosenvold > wrote:

Re: Version number for next commons-io

2015-09-21 Thread Phil Steitz
On 9/19/15 9:55 AM, sebb wrote: > On 19 September 2015 at 17:26, Kristian Rosenvold > wrote: >> 2015-09-19 13:58 GMT+02:00 Kristian Rosenvold : >>> Just to be clear on this, the breach is adding an interface to >> Oops. The breach is adding a /method/. > That's what I assumed - adding a method to

[site] please push update (was: svn commit: r1704337 - /commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml)

2015-09-21 Thread Bernd
Hello, can somebody please review this change and push it to the commons site? It removes the trunks-proper profile documentation, links to version 39 and adds some additional hints. Gruss Bend -- Forwarded message -- From: Date: 2015-09-21 18:00 GMT+02:00 Subject: svn commit:

Re: [COMPRESS] pkware header id for crypto extensions

2015-09-21 Thread Bear Giles
I have a moment to explain why the PKWARE crypto is stronger than the WinZip crypto. 1. The key has validation data, the VData and VCRC32 values. There are a couple different ways to compute a message integrity check that allows you to verify the encryption key and that the message contents have