Re: Welcome back Henri Biestro to the PMC
Hi Henri, Glad to see you back Siegfried Goeschl > On 13.06.2021, at 15:51, Gary Gregory wrote: > > Let's welcome back Henri Biestro to the PMC. > > Gary - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Welcome back Henri Biestro to the PMC
Cheers! Welcome back. -Rob > On Jun 13, 2021, at 11:44 AM, Matt Sicker wrote: > > Welcome back, Henri! Glad to see you again! > >> On Sun, Jun 13, 2021 at 08:52 Gary Gregory wrote: >> >> Let's welcome back Henri Biestro to the PMC. >> >> Gary >> - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [EXTERNAL] Re: [Numbers][All] Separate Java target version for "src/test"
On Sun, 13 Jun 2021 at 23:37, John Patrick wrote: > > So I want to start using Java 11 and take advantage of Java Modules. But > with a bug in Java Multi-Jar not supporting 1.8 as base and 11 upon that, > and most dependencies I want to upgrade eventually get stuck on a commons > project holding a pure JPMS solution. > > Potentially someone raise an enhancement to drop support for Java 1.8 which > isn't happening for Java 17, but for Java 18 which is only 8 month away it > could happen. So at that point it might be a shock for commons projects as > you might be blocking open source projects, or they roll off commons > projects... just a thought. > > I've tried to do a seamless upgrade, or suggest a roadmap, but haven't got > anywhere, but think I might just raise a JEP to drop 1.8 in Java 18... So Java is no longer always upwards compatible? I thought it was supposed to be "Write once, run anywhere". ? > John > > > On Thu, 10 Jun 2021 at 14:07, Gilles Sadowski wrote: > > > Le jeu. 10 juin 2021 à 14:42, John Patrick a > > écrit : > > > > > > If the tests are valid and useful once post Java 1.8, what about > > > starting the next release branch where the min version bumps to Java > > > 11. > > > > [Numbers] and related components were meant to replace and > > improve some functionalities provided in [Math] v3.6.1 whose > > target was Java 5 (!). > > A few years ago, the bump to Java 8 was considered a bold move > > (for "Commons"). :-} > > > > If we are sure that Java 11 is no problem for anyone who'd go > > through the upgrade effort, then indeed why not? > > > > Gilles > > > > > As Java 17 starting ramp down starts today I believe so in 3 months we > > > will have 3 LTS (1.8, 11 and 17) releases. So technically Java 18 > > > development starts tomorrow and I expect 1.8 will be dropped shortly > > > from backwards support as they want to get off the classpath fully and > > > onto the modules path. > > > > > > Anyway, just a thought. > > > > > > John > > > > > > On Thu, 10 Jun 2021 at 12:05, sebb wrote: > > > > > > > > Thanks. > > > > > > > > I've updated the RELEASE-NOTES accordingly (feel free to tweak the > > text) > > > > > > > > On Thu, 10 Jun 2021 at 00:58, Alex Herbert > > wrote: > > > > > > > > > > I have removed the requirement for Java 9 from the build. It is > > still used > > > > > in the performance testing module. > > > > > > > > > > Alex > > > > - > > 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: [EXTERNAL] Re: [Numbers][All] Separate Java target version for "src/test"
So I want to start using Java 11 and take advantage of Java Modules. But with a bug in Java Multi-Jar not supporting 1.8 as base and 11 upon that, and most dependencies I want to upgrade eventually get stuck on a commons project holding a pure JPMS solution. Potentially someone raise an enhancement to drop support for Java 1.8 which isn't happening for Java 17, but for Java 18 which is only 8 month away it could happen. So at that point it might be a shock for commons projects as you might be blocking open source projects, or they roll off commons projects... just a thought. I've tried to do a seamless upgrade, or suggest a roadmap, but haven't got anywhere, but think I might just raise a JEP to drop 1.8 in Java 18... John On Thu, 10 Jun 2021 at 14:07, Gilles Sadowski wrote: > Le jeu. 10 juin 2021 à 14:42, John Patrick a > écrit : > > > > If the tests are valid and useful once post Java 1.8, what about > > starting the next release branch where the min version bumps to Java > > 11. > > [Numbers] and related components were meant to replace and > improve some functionalities provided in [Math] v3.6.1 whose > target was Java 5 (!). > A few years ago, the bump to Java 8 was considered a bold move > (for "Commons"). :-} > > If we are sure that Java 11 is no problem for anyone who'd go > through the upgrade effort, then indeed why not? > > Gilles > > > As Java 17 starting ramp down starts today I believe so in 3 months we > > will have 3 LTS (1.8, 11 and 17) releases. So technically Java 18 > > development starts tomorrow and I expect 1.8 will be dropped shortly > > from backwards support as they want to get off the classpath fully and > > onto the modules path. > > > > Anyway, just a thought. > > > > John > > > > On Thu, 10 Jun 2021 at 12:05, sebb wrote: > > > > > > Thanks. > > > > > > I've updated the RELEASE-NOTES accordingly (feel free to tweak the > text) > > > > > > On Thu, 10 Jun 2021 at 00:58, Alex Herbert > wrote: > > > > > > > > I have removed the requirement for Java 9 from the build. It is > still used > > > > in the performance testing module. > > > > > > > > Alex > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: Welcome back Henri Biestro to the PMC
Thank you! Glad to be back. On 2021/06/13 15:44:22, Matt Sicker wrote: > Welcome back, Henri! Glad to see you again! > > On Sun, Jun 13, 2021 at 08:52 Gary Gregory wrote: > > > Let's welcome back Henri Biestro to the PMC. > > > > Gary > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Welcome back Henri Biestro to the PMC
Welcome back, Henri! Glad to see you again! On Sun, Jun 13, 2021 at 08:52 Gary Gregory wrote: > Let's welcome back Henri Biestro to the PMC. > > Gary >
[OT] Email client not displaying some emails: (was: [text][geometry] Move DoubleFormats utility to text)
On Sun, 13 Jun 2021 at 15:21, Matt Juntunen wrote: > > I've just discovered that my email client is not displaying some emails from > this thread (which is quite disconcerting to say the least) It looks like there are two copies [1], [2] of the original email. These show up a different threads in GMail and lists.a.o. The first thread [3] has a reply suggesting the creation of JIRA etc; the second thread [4] does not. Sebb [1] https://lists.apache.org/api/source.lua/r55ab50faeff4452292773f44ea38790dd9b6737f0accd2f8750e33cf@%3Cdev.commons.apache.org%3E [2] https://lists.apache.org/api/source.lua/rb2e544569f93862c09960666c9db7ed0985ebeff63729a187fa24807@%3Cdev.commons.apache.org%3E [3] https://lists.apache.org/thread.html/r55ab50faeff4452292773f44ea38790dd9b6737f0accd2f8750e33cf%40%3Cdev.commons.apache.org%3E [4] https://lists.apache.org/thread.html/rb2e544569f93862c09960666c9db7ed0985ebeff63729a187fa24807%40%3Cdev.commons.apache.org%3E - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [text][geometry] Move DoubleFormats utility to text
I've just discovered that my email client is not displaying some emails from this thread (which is quite disconcerting to say the least), so I completely missed the emails suggesting that I create a new JIRA issue and PR for this in text. I will go ahead and do that. I'll also make sure to include more format customization options in the PR as suggested. Thanks to everyone who replied here. Regards, Matt From: Matt Juntunen Sent: Saturday, June 12, 2021 11:31 AM To: Commons Developers List Subject: Re: [text][geometry] Move DoubleFormats utility to text If you're suggesting making the format symbols customizable, that would be a good improvement. I did not need that in commons-geometry so I did not add it. Note that I've recently created GEOMETRY-125 [1] for making the API for self-documenting and extensible. This could be a part of that. Any thoughts on including this functionality (if not the exact API) in commons-text? -Matt [1] https://issues.apache.org/jira/projects/GEOMETRY/issues/GEOMETRY-125 From: Gary Gregory Sent: Saturday, June 12, 2021 10:33 AM To: Commons Developers List Subject: Re: [text][geometry] Move DoubleFormats utility to text It's just a pointer to where the settings are in the JRE. Gary On Sat, Jun 12, 2021, 10:20 sebb wrote: > On Sat, 12 Jun 2021 at 14:00, Gary Gregory wrote: > > > > FTR: java.text.DecimalFormatSymbols > > Huh? > AFAICT the code does not use that class, so I have no idea what your > reply means. > > > Gary > > > > On Sat, Jun 12, 2021, 08:46 sebb wrote: > > > > > On Sat, 12 Jun 2021 at 12:58, Matt Juntunen > > > > wrote: > > > > > > > > Hello, > > > > > > > > I mentioned a while ago the idea of moving a utility that I find > quite > > > useful from commons-geometry to commons-text, which would be a more > > > appropriate home for it. There was not any interest at the time but > I've > > > made a few improvements to the class and I'd like to try again. The > utility > > > in question is the DoubleFormats [1] class. This class contains factory > > > methods for producing lightweight, thread-safe DoubleFunction > > > instances for converting doubles to decimal strings in different > formats. > > > The class is specifically designed for data output; no localization is > > > performed. > > > > > > No localisation? > > > Not even decimal point? > > > > > > > It is used in commons-geometry to provide a way to control the > precision > > > and formatting of double values in text-based geometric data formats > such > > > as OBJ. I've found that although the JDK provides a number of different > > > ways to format doubles (eg, String.format, DecimalFormat, BigDecimal, > etc), > > > none of them have fit the requirements for performant, thread-safe data > > > output. Hence, the reason for this class. > > > > > > > > Below are examples of each of the types of formats available and some > > > outputs. The arguments passed to each method are the precision (maximum > > > number of non-zero decimal digits) and min exponent (base 10 exponent > for > > > the smallest non-zero number that should be represented). > > > > > > > > // plain decimal representation; no scientific format > > > > DoubleFunction plain = DoubleFormats.createPlain(5, -3); > > > > plain.apply(1); // 1.0 > > > > plain.apply(1e10); // 100.0 > > > > plain.apply(1234.567); // 1234.6 > > > > plain.apply(0.00356); // 0.004 > > > > > > > > // scientific format > > > > DoubleFunction sci = DoubleFormats.createScientific(5, -3); > > > > sci.apply(1); // 1.0 > > > > sci.apply(1e10);// 1.0E10 > > > > sci.apply(1234.567);// 1.2346E3 > > > > sci.apply(0.00356); // 4.0E-3 > > > > > > > > // engineering format > > > > DoubleFunction eng = DoubleFormats.createEngineering(5, -3); > > > > eng.apply(1); // 1.0 > > > > eng.apply(1e10);// 10.0E9 > > > > eng.apply(1234.567);// 1.2346E3 > > > > eng.apply(0.00356); // 4.0E-3 > > > > > > > > // default format; uses the Double.toString() convention of > representing > > > > // numbers less that 10^-3 or greater than 10^7 using scientific > format > > > and > > > > // other numbers using plain decimal format > > > > DoubleFunction def = DoubleFormats.createDefault(5, -3); > > > > def.apply(1); // 1.0 > > > > def.apply(1e10);// 1.0E10 > > > > def.apply(1234.567);// 1234.6 > > > > def.apply(0.00356); // 0.004 > > > > > > > > > > > > The performance of all of these methods is comparable to > DecimalFormat > > > or BigDecimal. The benchmark output below shows the results of > formatting > > > 1 double values using standard Double.toString(), a simple > BigDecimal > > > conversion, DecimalFormat (single instance), and a function returned > from > > > DoubleFormats.createDefault(). Double.toString() is the clear winner > but > > > the rest are all quite close. > > > > > > > > Benchmark
[VOTE][RESULT] Release Apache Commons IO 2.10.0 based on RC1
This VOTE passes with the following binding +1 votes: - Henri Biestro - Matt Sicker - Gary Gregory Gary On Sun, Jun 13, 2021 at 9:54 AM Gary Gregory wrote: > > My +1 > > Gary > > On Thu, Jun 10, 2021 at 9:01 AM Gary Gregory wrote: > > > > We have fixed a few bugs and added some enhancements since Apache > > Commons IO 2.9.0 was released, so I would like to release Apache > > Commons IO 2.10.0. > > > > Apache Commons IO 2.10.0 RC1 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1 (svn > > revision 48259) > > > > The Git tag commons-io-2.10.0-RC1 commit for this RC is > > a73895fbefd57c23595a5e9e85f0649993c59080 which you can browse here: > > > > https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=a73895fbefd57c23595a5e9e85f0649993c59080 > > You may checkout this tag using: > > git clone https://gitbox.apache.org/repos/asf/commons-io.git > > --branch commons-io-2.10.0-RC1 commons-io-2.10.0-RC1 > > > > Maven artifacts are here: > > > > https://repository.apache.org/content/repositories/orgapachecommons-1551/commons-io/commons-io/2.10.0/ > > > > These are the artifacts and their hashes: > > > > #Release SHA-512s > > #Thu Jun 10 08:43:37 EDT 2021 > > commons-io-2.10.0-bin.tar.gz=14c08c93379e975ca28723086acc4c1ba9acb99ed4a36e21ea6cdf9eeebac53cb08f5f606ade69daa58af4aa7c56b4b286cf96d36604139d5de9ee3902fc09b9 > > commons-io-2.10.0-bin.zip=a5e32c8dbf76779247fb233646631e213b125c655a299edea895dfaddd86672fbe91396c548100b4d35d5647005066850243704d751d25028ecd13cafc3f36d8 > > commons-io-2.10.0-javadoc.jar=ecdd571aa8de94e41c1d507384fddcd52d845687b10471ef5641033040d4209eed28c5018bd2e3283233132c70ad9188c604c586e36f4bbb93fe748c4713ebc7 > > commons-io-2.10.0-sources.jar=8152939638af55595858a7214e9a38804911b1f8e7a7a9d49c1456e258577bfc72671915d33c05d33e40f41c14e0090ddc2789e7ba0020c8f391448ae14d735d > > commons-io-2.10.0-src.tar.gz=227a2293c4e0ab209da1a78db07e93a940c45393dfc48764552c432c37bed974f1cff6379edd4240bec8d635919e4a7008ce39687ce43ae3463cee42337a3335 > > commons-io-2.10.0-src.zip=6f6088ec14c896ea84b4e31867925d51b770c7750d7ca108296b778fa0b45fe70514a3f590ad1f00343ad5adb7882d9a905237f30a07058c5ab80e51b072f402 > > commons-io-2.10.0-test-sources.jar=2591d6038d829f3ec0b58a00bc4e884ce37ebace91a7ec7cad364419d13bebec5a98a7cadb8fa2534f9f98a1b0718bb669311125054f2ace85c985c1f074ee2d > > commons-io-2.10.0-tests.jar=b5eddbdc6c2b335e1afc08ce64acc9a008396839384fcdb61790d536eb96e5d920cfb213eaeee9b9d8368d45f9f2c0b9625babaf2c0ac1ee6c4d68c977461061 > > > > > > > > I have tested this with 'mvn -V -Prelease -Ptest-deploy -P jacoco -P > > japicmp clean package site deploy' using: > > > > Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d) > > Maven home: /usr/local/Cellar/maven/3.8.1/libexec > > Java version: 1.8.0_292, vendor: AdoptOpenJDK, runtime: > > /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" > > > > Details of changes since 2.9.0 are in the release notes: > > > > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/RELEASE-NOTES.txt > > > > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/site/changes-report.html > > > > Site: > > > > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/site/index.html > > (note some *relative* links are broken and the 2.10.0 directories > > are not yet created - these will be OK once the site is deployed.) > > > > JApiCmp Report (compared to 2.9.0): > > > > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/site/japicmp.html > > > > RAT Report: > > > > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/site/rat-report.html > > > > KEYS: > > https://www.apache.org/dist/commons/KEYS > > > > Please review the release candidate and vote. > > This vote will close no sooner than 72 hours from now. > > > > [ ] +1 Release these artifacts > > [ ] +0 OK, but... > > [ ] -0 OK, but really should fix... > > [ ] -1 I oppose this release because... > > > > Thank you, > > > > Gary Gregory, > > Release Manager (using key 86fdc7e2a11262cb) > > > > For following is intended as a helper and refresher for reviewers. > > > > Validating a release candidate > > == > > > > These guidelines are NOT complete. > > > > Requirements: Git, Java, Maven. > > > > You can validate a release from a release candidate (RC) tag as follows. > > > > 1) Clone and checkout the RC tag > > > > git clone https://gitbox.apache.org/repos/asf/commons-io.git --branch > > commons-io-2.10.0-RC1 commons-io-2.10.0-RC1 > > cd commons-io-2.10.0-RC1 > > > > 2) Check Apache licenses > > > > This step is not required if the site includes a RAT report page which > > you then must check. > > > > mvn apache-rat:check > > > > 3) Check binary compatibility > > > > Older components still use Apache Clirr: > > > >
Re: [VOTE] Release Apache Commons IO 2.10.0 based on RC1
My +1 Gary On Thu, Jun 10, 2021 at 9:01 AM Gary Gregory wrote: > > We have fixed a few bugs and added some enhancements since Apache > Commons IO 2.9.0 was released, so I would like to release Apache > Commons IO 2.10.0. > > Apache Commons IO 2.10.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1 (svn > revision 48259) > > The Git tag commons-io-2.10.0-RC1 commit for this RC is > a73895fbefd57c23595a5e9e85f0649993c59080 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=a73895fbefd57c23595a5e9e85f0649993c59080 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-io.git > --branch commons-io-2.10.0-RC1 commons-io-2.10.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1551/commons-io/commons-io/2.10.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Thu Jun 10 08:43:37 EDT 2021 > commons-io-2.10.0-bin.tar.gz=14c08c93379e975ca28723086acc4c1ba9acb99ed4a36e21ea6cdf9eeebac53cb08f5f606ade69daa58af4aa7c56b4b286cf96d36604139d5de9ee3902fc09b9 > commons-io-2.10.0-bin.zip=a5e32c8dbf76779247fb233646631e213b125c655a299edea895dfaddd86672fbe91396c548100b4d35d5647005066850243704d751d25028ecd13cafc3f36d8 > commons-io-2.10.0-javadoc.jar=ecdd571aa8de94e41c1d507384fddcd52d845687b10471ef5641033040d4209eed28c5018bd2e3283233132c70ad9188c604c586e36f4bbb93fe748c4713ebc7 > commons-io-2.10.0-sources.jar=8152939638af55595858a7214e9a38804911b1f8e7a7a9d49c1456e258577bfc72671915d33c05d33e40f41c14e0090ddc2789e7ba0020c8f391448ae14d735d > commons-io-2.10.0-src.tar.gz=227a2293c4e0ab209da1a78db07e93a940c45393dfc48764552c432c37bed974f1cff6379edd4240bec8d635919e4a7008ce39687ce43ae3463cee42337a3335 > commons-io-2.10.0-src.zip=6f6088ec14c896ea84b4e31867925d51b770c7750d7ca108296b778fa0b45fe70514a3f590ad1f00343ad5adb7882d9a905237f30a07058c5ab80e51b072f402 > commons-io-2.10.0-test-sources.jar=2591d6038d829f3ec0b58a00bc4e884ce37ebace91a7ec7cad364419d13bebec5a98a7cadb8fa2534f9f98a1b0718bb669311125054f2ace85c985c1f074ee2d > commons-io-2.10.0-tests.jar=b5eddbdc6c2b335e1afc08ce64acc9a008396839384fcdb61790d536eb96e5d920cfb213eaeee9b9d8368d45f9f2c0b9625babaf2c0ac1ee6c4d68c977461061 > > > > I have tested this with 'mvn -V -Prelease -Ptest-deploy -P jacoco -P > japicmp clean package site deploy' using: > > Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d) > Maven home: /usr/local/Cellar/maven/3.8.1/libexec > Java version: 1.8.0_292, vendor: AdoptOpenJDK, runtime: > /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" > > Details of changes since 2.9.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/site/index.html > (note some *relative* links are broken and the 2.10.0 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 2.9.0): > > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/site/rat-report.html > > KEYS: > https://www.apache.org/dist/commons/KEYS > > Please review the release candidate and vote. > This vote will close no sooner than 72 hours from now. > > [ ] +1 Release these artifacts > [ ] +0 OK, but... > [ ] -0 OK, but really should fix... > [ ] -1 I oppose this release because... > > Thank you, > > Gary Gregory, > Release Manager (using key 86fdc7e2a11262cb) > > For following is intended as a helper and refresher for reviewers. > > Validating a release candidate > == > > These guidelines are NOT complete. > > Requirements: Git, Java, Maven. > > You can validate a release from a release candidate (RC) tag as follows. > > 1) Clone and checkout the RC tag > > git clone https://gitbox.apache.org/repos/asf/commons-io.git --branch > commons-io-2.10.0-RC1 commons-io-2.10.0-RC1 > cd commons-io-2.10.0-RC1 > > 2) Check Apache licenses > > This step is not required if the site includes a RAT report page which > you then must check. > > mvn apache-rat:check > > 3) Check binary compatibility > > Older components still use Apache Clirr: > > This step is not required if the site includes a Clirr report page > which you then must check. > > mvn clirr:check > > Newer components use JApiCmp with the japicmp Maven Profile: > > This step is not required if the site includes a JApiCmp report page > which you then must check. > > mvn install -DskipTests -P japicmp japicmp:cmp > > 4) Build the package > > mvn -V clean package > > You can
Welcome back Henri Biestro to the PMC
Let's welcome back Henri Biestro to the PMC. Gary
Re: [VOTE] Release Apache Commons IO 2.10.0 based on RC1
Tried on a Windows machine, no pb. Retried on the Mac after nuking commons parent 51 from .m2 and everything went smoothly. Sorry for the scare. Checked on Java11 for good measure. :-) henri.biestro@L-HBIESTRO-4 commons-io % mvn -V clean install site Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-04T21:00:29+02:00) Maven home: /Users/henri.biestro/Java/apache-maven-3.6.1 Java version: 11.0.1, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home Default locale: en_FR, platform encoding: UTF-8 OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" On 2021/06/13 11:31:28, Gary Gregory wrote: > Yeah, coincidentally, I had to delete my Maven cache this week to fix an > unrelated corrupted file and nuking the whole thing was simplest. > > Gary > > On Sun, Jun 13, 2021, 01:32 Henri Biestro wrote: > > > The parent POM is 52, no pb there; executing 'mvn site', the SpotBugs > > report target has a dependency on commons-text-1.9 complaining about > > commons-parent-51. Had to build one locally to overcome, download from repo > > seemed to be a 0 bytes artefact. First build of commons-io on that machine, > > probably something funky on my end (corrupted .m2?). > > Henrib > > > > On 2021/06/12 18:28:52, Gary Gregory wrote: > > > The parent POM version should be 52. Are you sure you are seing 51? > > > > > > Gary > > > > > > > > > On Sat, Jun 12, 2021, 06:09 Henri Biestro wrote: > > > > > > > Using: mvn -V clean install site > > > > Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; > > > > 2019-04-04T21:00:29+02:00) > > > > Maven home: /Users/henri.biestro/Java/apache-maven-3.6.1 > > > > Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: > > > > /Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home/jre > > > > Default locale: en_FR, platform encoding: UTF-8 > > > > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "Mac" > > > > > > > > Checked the various site reports, all check OK. > > > > (As a side note, Maven had a hard time resolving a reference to > > > > commons-parent-51 for the SpotBugs report, may be a pb on my side). > > > > > > > > Checked the jar signature, OK. > > > > henri.biestro@L-HBIESTRO Downloads % gpg2 --verify > > > > commons-io-2.10.0.jar.asc > > > > gpg: assuming signed data in 'commons-io-2.10.0.jar' > > > > gpg: Signature made Thu Jun 10 14:43:36 2021 CEST > > > > gpg:using RSA key > > 2DB4F1EF0FA761ECC4EA935C86FDC7E2A11262CB > > > > gpg: Good signature from "Gary David Gregory (Code signing key) < > > > > ggreg...@apache.org>" [unknown] > > > > gpg: WARNING: This key is not certified with a trusted signature! > > > > gpg: There is no indication that the signature belongs to the > > > > owner. > > > > Primary key fingerprint: 2DB4 F1EF 0FA7 61EC C4EA 935C 86FD C7E2 A112 > > 62CB > > > > > > > > Vote [+1] (pending my reintroduction as PMC member :-) ). > > > > > > > > Cheers! > > > > > > > > On 2021/06/10 13:01:54, Gary Gregory wrote: > > > > > We have fixed a few bugs and added some enhancements since Apache > > > > > Commons IO 2.9.0 was released, so I would like to release Apache > > > > > Commons IO 2.10.0. > > > > > > > > > > Apache Commons IO 2.10.0 RC1 is available for review here: > > > > > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1 > > (svn > > > > > revision 48259) > > > > > > > > > > The Git tag commons-io-2.10.0-RC1 commit for this RC is > > > > > a73895fbefd57c23595a5e9e85f0649993c59080 which you can browse here: > > > > > > > > > > > https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=a73895fbefd57c23595a5e9e85f0649993c59080 > > > > > You may checkout this tag using: > > > > > git clone https://gitbox.apache.org/repos/asf/commons-io.git > > > > > --branch commons-io-2.10.0-RC1 commons-io-2.10.0-RC1 > > > > > > > > > > Maven artifacts are here: > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachecommons-1551/commons-io/commons-io/2.10.0/ > > > > > > > > > > These are the artifacts and their hashes: > > > > > > > > > > #Release SHA-512s > > > > > #Thu Jun 10 08:43:37 EDT 2021 > > > > > > > > > > > commons-io-2.10.0-bin.tar.gz=14c08c93379e975ca28723086acc4c1ba9acb99ed4a36e21ea6cdf9eeebac53cb08f5f606ade69daa58af4aa7c56b4b286cf96d36604139d5de9ee3902fc09b9 > > > > > > > > > > > commons-io-2.10.0-bin.zip=a5e32c8dbf76779247fb233646631e213b125c655a299edea895dfaddd86672fbe91396c548100b4d35d5647005066850243704d751d25028ecd13cafc3f36d8 > > > > > > > > > > > commons-io-2.10.0-javadoc.jar=ecdd571aa8de94e41c1d507384fddcd52d845687b10471ef5641033040d4209eed28c5018bd2e3283233132c70ad9188c604c586e36f4bbb93fe748c4713ebc7 > > > > > > > > > > > commons-io-2.10.0-sources.jar=8152939638af55595858a7214e9a38804911b1f8e7a7a9d49c1456e258577bfc72671915d33c05d33e40f41c14e0090ddc2789e7ba0020c8f391448ae14d735d > > > > > > > > > > >
Re: [VOTE] Release Apache Commons IO 2.10.0 based on RC1
Yeah, coincidentally, I had to delete my Maven cache this week to fix an unrelated corrupted file and nuking the whole thing was simplest. Gary On Sun, Jun 13, 2021, 01:32 Henri Biestro wrote: > The parent POM is 52, no pb there; executing 'mvn site', the SpotBugs > report target has a dependency on commons-text-1.9 complaining about > commons-parent-51. Had to build one locally to overcome, download from repo > seemed to be a 0 bytes artefact. First build of commons-io on that machine, > probably something funky on my end (corrupted .m2?). > Henrib > > On 2021/06/12 18:28:52, Gary Gregory wrote: > > The parent POM version should be 52. Are you sure you are seing 51? > > > > Gary > > > > > > On Sat, Jun 12, 2021, 06:09 Henri Biestro wrote: > > > > > Using: mvn -V clean install site > > > Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; > > > 2019-04-04T21:00:29+02:00) > > > Maven home: /Users/henri.biestro/Java/apache-maven-3.6.1 > > > Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: > > > /Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home/jre > > > Default locale: en_FR, platform encoding: UTF-8 > > > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "Mac" > > > > > > Checked the various site reports, all check OK. > > > (As a side note, Maven had a hard time resolving a reference to > > > commons-parent-51 for the SpotBugs report, may be a pb on my side). > > > > > > Checked the jar signature, OK. > > > henri.biestro@L-HBIESTRO Downloads % gpg2 --verify > > > commons-io-2.10.0.jar.asc > > > gpg: assuming signed data in 'commons-io-2.10.0.jar' > > > gpg: Signature made Thu Jun 10 14:43:36 2021 CEST > > > gpg:using RSA key > 2DB4F1EF0FA761ECC4EA935C86FDC7E2A11262CB > > > gpg: Good signature from "Gary David Gregory (Code signing key) < > > > ggreg...@apache.org>" [unknown] > > > gpg: WARNING: This key is not certified with a trusted signature! > > > gpg: There is no indication that the signature belongs to the > > > owner. > > > Primary key fingerprint: 2DB4 F1EF 0FA7 61EC C4EA 935C 86FD C7E2 A112 > 62CB > > > > > > Vote [+1] (pending my reintroduction as PMC member :-) ). > > > > > > Cheers! > > > > > > On 2021/06/10 13:01:54, Gary Gregory wrote: > > > > We have fixed a few bugs and added some enhancements since Apache > > > > Commons IO 2.9.0 was released, so I would like to release Apache > > > > Commons IO 2.10.0. > > > > > > > > Apache Commons IO 2.10.0 RC1 is available for review here: > > > > https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1 > (svn > > > > revision 48259) > > > > > > > > The Git tag commons-io-2.10.0-RC1 commit for this RC is > > > > a73895fbefd57c23595a5e9e85f0649993c59080 which you can browse here: > > > > > > > > https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=a73895fbefd57c23595a5e9e85f0649993c59080 > > > > You may checkout this tag using: > > > > git clone https://gitbox.apache.org/repos/asf/commons-io.git > > > > --branch commons-io-2.10.0-RC1 commons-io-2.10.0-RC1 > > > > > > > > Maven artifacts are here: > > > > > > > > https://repository.apache.org/content/repositories/orgapachecommons-1551/commons-io/commons-io/2.10.0/ > > > > > > > > These are the artifacts and their hashes: > > > > > > > > #Release SHA-512s > > > > #Thu Jun 10 08:43:37 EDT 2021 > > > > > > > > commons-io-2.10.0-bin.tar.gz=14c08c93379e975ca28723086acc4c1ba9acb99ed4a36e21ea6cdf9eeebac53cb08f5f606ade69daa58af4aa7c56b4b286cf96d36604139d5de9ee3902fc09b9 > > > > > > > > commons-io-2.10.0-bin.zip=a5e32c8dbf76779247fb233646631e213b125c655a299edea895dfaddd86672fbe91396c548100b4d35d5647005066850243704d751d25028ecd13cafc3f36d8 > > > > > > > > commons-io-2.10.0-javadoc.jar=ecdd571aa8de94e41c1d507384fddcd52d845687b10471ef5641033040d4209eed28c5018bd2e3283233132c70ad9188c604c586e36f4bbb93fe748c4713ebc7 > > > > > > > > commons-io-2.10.0-sources.jar=8152939638af55595858a7214e9a38804911b1f8e7a7a9d49c1456e258577bfc72671915d33c05d33e40f41c14e0090ddc2789e7ba0020c8f391448ae14d735d > > > > > > > > commons-io-2.10.0-src.tar.gz=227a2293c4e0ab209da1a78db07e93a940c45393dfc48764552c432c37bed974f1cff6379edd4240bec8d635919e4a7008ce39687ce43ae3463cee42337a3335 > > > > > > > > commons-io-2.10.0-src.zip=6f6088ec14c896ea84b4e31867925d51b770c7750d7ca108296b778fa0b45fe70514a3f590ad1f00343ad5adb7882d9a905237f30a07058c5ab80e51b072f402 > > > > > > > > commons-io-2.10.0-test-sources.jar=2591d6038d829f3ec0b58a00bc4e884ce37ebace91a7ec7cad364419d13bebec5a98a7cadb8fa2534f9f98a1b0718bb669311125054f2ace85c985c1f074ee2d > > > > > > > > commons-io-2.10.0-tests.jar=b5eddbdc6c2b335e1afc08ce64acc9a008396839384fcdb61790d536eb96e5d920cfb213eaeee9b9d8368d45f9f2c0b9625babaf2c0ac1ee6c4d68c977461061 > > > > > > > > > > > > > > > > I have tested this with 'mvn -V -Prelease -Ptest-deploy -P jacoco -P > > > > japicmp clean package site deploy' using: > > > > > > > > Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d) > > > > Maven
Re: [text][geometry] Move DoubleFormats utility to text
On Sat, 12 Jun 2021 at 16:32, Matt Juntunen wrote: > > If you're suggesting making the format symbols customizable, that would be a > good improvement. I did not need that in commons-geometry so I did not add > it. Note that I've recently created GEOMETRY-125 [1] for making the API for > self-documenting and extensible. This could be a part of that. > > Any thoughts on including this functionality (if not the exact API) in > commons-text? I agree that it is a reasonable fit for Commons Text. If it is to be included, IMO it must support localised symbols. > -Matt > > [1] https://issues.apache.org/jira/projects/GEOMETRY/issues/GEOMETRY-125 > > From: Gary Gregory > Sent: Saturday, June 12, 2021 10:33 AM > To: Commons Developers List > Subject: Re: [text][geometry] Move DoubleFormats utility to text > > It's just a pointer to where the settings are in the JRE. > > Gary > > On Sat, Jun 12, 2021, 10:20 sebb wrote: > > > On Sat, 12 Jun 2021 at 14:00, Gary Gregory wrote: > > > > > > FTR: java.text.DecimalFormatSymbols > > > > Huh? > > AFAICT the code does not use that class, so I have no idea what your > > reply means. > > > > > Gary > > > > > > On Sat, Jun 12, 2021, 08:46 sebb wrote: > > > > > > > On Sat, 12 Jun 2021 at 12:58, Matt Juntunen > > > > > > wrote: > > > > > > > > > > Hello, > > > > > > > > > > I mentioned a while ago the idea of moving a utility that I find > > quite > > > > useful from commons-geometry to commons-text, which would be a more > > > > appropriate home for it. There was not any interest at the time but > > I've > > > > made a few improvements to the class and I'd like to try again. The > > utility > > > > in question is the DoubleFormats [1] class. This class contains factory > > > > methods for producing lightweight, thread-safe DoubleFunction > > > > instances for converting doubles to decimal strings in different > > formats. > > > > The class is specifically designed for data output; no localization is > > > > performed. > > > > > > > > No localisation? > > > > Not even decimal point? > > > > > > > > > It is used in commons-geometry to provide a way to control the > > precision > > > > and formatting of double values in text-based geometric data formats > > such > > > > as OBJ. I've found that although the JDK provides a number of different > > > > ways to format doubles (eg, String.format, DecimalFormat, BigDecimal, > > etc), > > > > none of them have fit the requirements for performant, thread-safe data > > > > output. Hence, the reason for this class. > > > > > > > > > > Below are examples of each of the types of formats available and some > > > > outputs. The arguments passed to each method are the precision (maximum > > > > number of non-zero decimal digits) and min exponent (base 10 exponent > > for > > > > the smallest non-zero number that should be represented). > > > > > > > > > > // plain decimal representation; no scientific format > > > > > DoubleFunction plain = DoubleFormats.createPlain(5, -3); > > > > > plain.apply(1); // 1.0 > > > > > plain.apply(1e10); // 100.0 > > > > > plain.apply(1234.567); // 1234.6 > > > > > plain.apply(0.00356); // 0.004 > > > > > > > > > > // scientific format > > > > > DoubleFunction sci = DoubleFormats.createScientific(5, -3); > > > > > sci.apply(1); // 1.0 > > > > > sci.apply(1e10);// 1.0E10 > > > > > sci.apply(1234.567);// 1.2346E3 > > > > > sci.apply(0.00356); // 4.0E-3 > > > > > > > > > > // engineering format > > > > > DoubleFunction eng = DoubleFormats.createEngineering(5, -3); > > > > > eng.apply(1); // 1.0 > > > > > eng.apply(1e10);// 10.0E9 > > > > > eng.apply(1234.567);// 1.2346E3 > > > > > eng.apply(0.00356); // 4.0E-3 > > > > > > > > > > // default format; uses the Double.toString() convention of > > representing > > > > > // numbers less that 10^-3 or greater than 10^7 using scientific > > format > > > > and > > > > > // other numbers using plain decimal format > > > > > DoubleFunction def = DoubleFormats.createDefault(5, -3); > > > > > def.apply(1); // 1.0 > > > > > def.apply(1e10);// 1.0E10 > > > > > def.apply(1234.567);// 1234.6 > > > > > def.apply(0.00356); // 0.004 > > > > > > > > > > > > > > > The performance of all of these methods is comparable to > > DecimalFormat > > > > or BigDecimal. The benchmark output below shows the results of > > formatting > > > > 1 double values using standard Double.toString(), a simple > > BigDecimal > > > > conversion, DecimalFormat (single instance), and a function returned > > from > > > > DoubleFormats.createDefault(). Double.toString() is the clear winner > > but > > > > the rest are all quite close. > > > > > > > > > > Benchmark (size) Mode Cnt > > > > ScoreError Units > > > > > DoubleFormatsPerformance.doubleToString 1 avgt5 > > > > 3837610.399 ± 62668.705
