Re: [commons-io] question: file content merge sort and binary search

2023-07-20 Thread ssz
Hi Sure, I will support my code. I have a lot of other opensource projects, not so much free time. But this code will have the highest priority as Commons is used by thousands of developers. My other projects are used by hundreds of people. On Wed, Jul 19, 2023 at 8:28 PM Gilles Sadowski wrote:

Re: [commons-io] question: file content merge sort and binary search

2023-07-20 Thread Gilles Sadowski
Hi. [Disclaimer: I'm not a user nor a developer of "Commons IO", so I'm not the most suitable for entertaining this conversation and, surely, I shouldn't be the only one...] Le jeu. 20 juil. 2023 à 10:33, ssz a écrit : > > Hi > Sure, I will support my code. > I have a lot of other opensource

Re: [commons-io] question: file content merge sort and binary search

2023-07-20 Thread Gary Gregory
I already commented elsewhere (can't recall if it was on this list or github) on why this is not a good fit for IO. Too much like a database operation, IO is a lower level library, and so on. IO is not a kitchen sink for anything related to IO. Like Lang, it was initially conceived as a library

Re: [commons-io] question: file content merge sort and binary search

2023-07-20 Thread ssz
> Which projects (ASF?) depend on your proposed contribution? Currently only business projects, not opensource. I'm thinking about RDF-Graph backed by FS. If I implement this solution I will raise an issue with the Apache Jena team. The original library will probably support multiplatform, in

Re: [commons-io] question: file content merge sort and binary search

2023-07-20 Thread ssz
That's great! - But ANT is quite an ancient system, and it is now relatively unknown. - And it is relatively heavy. Maybe it's better to have single-function in the dedicated library or in well-known library with other useful features - It uses in-memory sorting:

Re: [commons-io] question: file content merge sort and binary search

2023-07-20 Thread Gary Gregory
Note that Apache Ant already provides similar functionality: https://ant.apache.org/manual/api/org/apache/tools/ant/filters/SortFilter.html Gary On Thu, Jul 20, 2023, 07:38 Gilles Sadowski wrote: > Hi. > > [Disclaimer: I'm not a user nor a developer of "Commons IO", so > I'm not the most

Re: [commons-io] question: file content merge sort and binary search

2023-07-20 Thread ssz
For sure, you can sort in-memory, no problem here. I think we need to find a well-known library with non-in-memory sorting and binary searching, it is better relatively new (java8+) On Thu, Jul 20, 2023 at 3:08 PM ssz wrote: > That's great! > - But ANT is quite an ancient system, and it is now

Re: [math] JIRA ticket for modularisation of all 14 legacy packages

2023-07-20 Thread Gilles Sadowski
Hello. Le mer. 19 juil. 2023 à 12:59, Dimitrios Efthymiou a écrit : > > [...] > 1-- [...] > 2--As for the atomic refactoring and feature branch, well, > unless someone moves the Variance class (you said that someone > is doing it now) and the distance package and whatever other > dependencies

Re: [commons-io] question: file content merge sort and binary search

2023-07-20 Thread ssz
> I already commented elsewhere on why this is not a good fit for IO My bad, I did not realise that discussion is closed with final resolution. I read "what do others think?" and thought that it is about continuing discussion. > Instead of keeping on arguing to shove your library in IO I

Re: [commons-io] question: file content merge sort and binary search

2023-07-20 Thread Gilles Sadowski
Le jeu. 20 juil. 2023 à 15:18, Gary Gregory a écrit : > > [...] Instead of keeping on arguing to shove your library in [...] If we could stop the brutal language... (?) The OP asked politely, and was ready to wait indefinitely (unsubscribing from this ML) for an answer; I just wanted to make

Re: [math] JIRA ticket for modularisation of all 14 legacy packages

2023-07-20 Thread Dimitrios Efthymiou
are you saying that in order to move the ml.clustering classes to the new clustering module, I can take all the dependencies to classes and their transitive dependencies, copy them to the new clustering module, but only keep in them the minimum required code for the new module to operate? On Thu,

[ANNOUNCE] Apache Commons FileUpload 2.0.0-M1

2023-07-20 Thread Gary Gregory
The Apache Commons FileUpload Parent team is pleased to announce the release of Apache Commons FileUpload Parent 2.0.0-M1. The Apache Commons FileUpload component provides a simple yet flexible means of adding support for multipart file upload functionality to servlets and web applications. This

Re: [math] JIRA ticket for modularisation of all 14 legacy packages

2023-07-20 Thread Dimitrios Efthymiou
I am not home now, but these are the ones i remember from looking at the GitHub repo: AbstractStorelessUnivariateStatistic.java AbstractUnivariateStatistic.java WeightedEvaluation.java Sum.java FirstMoment.java Mean.java SecondMoment.java StandardDeviation.java Variance.java VectorialMean.java On

Re: [math] JIRA ticket for modularisation of all 14 legacy packages

2023-07-20 Thread Dimitrios Efthymiou
I am not home now, but these are the ones i remember from looking at the GitHub repo: AbstractStorelessUnivariateStatistic.java AbstractUnivariateStatistic.java WeightedEvaluation.java Sum.java FirstMoment.java Mean.java SecondMoment.java StandardDeviation.java Variance.java VectorialMean.java

Re: [math] JIRA ticket for modularisation of all 14 legacy packages

2023-07-20 Thread Gilles Sadowski
Le jeu. 20 juil. 2023 à 23:46, Dimitrios Efthymiou a écrit : > > I am not home now, but these are the ones i remember from looking at the > GitHub repo: > AbstractStorelessUnivariateStatistic.java > AbstractUnivariateStatistic.java > WeightedEvaluation.java > Sum.java > FirstMoment.java >

Re: [math] JIRA ticket for modularisation of all 14 legacy packages

2023-07-20 Thread Dimitrios Efthymiou
Unfortunately, i just tried a simple move, but there are deoendencies on 3 distance classes and about 12 stats classes, because there are transitive dependencies. Not to mention the respective test classes. On Thu, 20 Jul 2023, 22:22 Gilles Sadowski, wrote: > Le jeu. 20 juil. 2023 à 21:19,

Re: [math] JIRA ticket for modularisation of all 14 legacy packages

2023-07-20 Thread Gilles Sadowski
Le jeu. 20 juil. 2023 à 23:28, Dimitrios Efthymiou a écrit : > > Unfortunately, i just tried a simple move, but there are deoendencies on 3 > distance classes But... those classes are only used by the "clustering" package; they are not external dependencies; they would go into the new module as

Re: [math] JIRA ticket for modularisation of all 14 legacy packages

2023-07-20 Thread Gilles Sadowski
Le jeu. 20 juil. 2023 à 21:19, Dimitrios Efthymiou a écrit : > > are you saying that in order to move the ml.clustering classes > to the new clustering module, I can take all the dependencies to classes > and their transitive dependencies, copy them to the new clustering module, > but only keep

[pool] Another source compatibility break in 2.x

2023-07-20 Thread Phil Steitz
We have a minor source compat break still in 2.x The change to have BaseGenericObjectPool implement Autocloseable forced addition of an abstract close method. Technically, that could break subclass implementations that don't implement close. I see three options here. Maybe someone else has a

Re: [commons-pool] branch POOL_2_X updated: Add Duration named APIs and deprecate old APIs.

2023-07-20 Thread Gary Gregory
Hi Phil, There can get some ambiguity for me when I read code like (unless you know the API inside and out and use it on the daily): somePoolThing.getFooTime() Some of our methods return a Duration and others an Instant, so there, I think the type in the method name makes sense. Then, for a bit

Re: [commons-pool] branch POOL_2_X updated: Add Duration named APIs and deprecate old APIs.

2023-07-20 Thread Phil Steitz
OK, I get it now. I am just worried about making people change things twice - first to a method that takes Duration rather than long and then to another one that does the same thing but now has a different name. How about leaving the 2.x names as is, not adding new methods with the same