Re: [VOTE] Release Apache Commons IO 2.17.0 based on RC1
My +1 Gary On Sun, Sep 15, 2024 at 1:57 PM Gary Gregory wrote: > > We have fixed a few bugs and added enhancements since Apache Commons > IO 2.16.1 was released, so I would like to release Apache Commons IO > 2.17.0. > > Apache Commons IO 2.17.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/io/2.17.0-RC1 (svn > revision 71599) > > The Git tag commons-io-2.17.0-RC1 commit for this RC is > 7b5c3ec3ddcedeb764fa79f29e9baefdd3444163 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=7b5c3ec3ddcedeb764fa79f29e9baefdd3444163 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-io.git > --branch commons-io-2.17.0-RC1 commons-io-2.17.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1779/commons-io/commons-io/2.17.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sun Sep 15 15:31:05 UTC 2024 > commons-io-2.17.0-bin.tar.gz=1e9b1c4a0c63cf0abe904ddf811a40b12d15de908da487dc8ce7517e2f8c15d22bb7f8b1d5cf334b27b9a601749db0e429a8d4e82dc9a778662d0923b0fc8c0d > commons-io-2.17.0-bin.zip=b969309c369067853fa885f00b10815b0893b92d830c936e52f992daa4a1549550461f552a806d5774b1d54992d2f77ffca1a1591cc5e0ef7387a796d6ae3b9f > commons-io-2.17.0-bom.json=9c55af01f0179a95380ac490261afad818bac3d0bec2b5e7d7ef27235dfe9b9377203177fa2a05741500225f2688d60f7fb1ce23a0aa0f364f7bcf1b12c8be11 > commons-io-2.17.0-bom.xml=6a2116e934455facbbcd9aa3de205fab7713e632c06cf769f987d6dd1b71cfad8920a5094f2fc24e9acd0dca59cc80184d978c837b716da39898e05317cf1112 > commons-io-2.17.0-javadoc.jar=e9d977d641280d6d0f14d9e51759bdec02d9a5c5b1af98ad1b63cbdca4e58074188c4d128a901fc6bbd6e491e1310ee19d34c88410b9f8da06c854121078b301 > commons-io-2.17.0-sources.jar=174b12dc3dc43a30942a1702b2b97d8e4c15a6568125697775e314f7c4aa34e3fc2282b42b56223c419feda7a97feb7b0696969885c633c64d0c6c29b476c57a > commons-io-2.17.0-src.tar.gz=5681b7bab9e34e9051e4f7a48925ecdf5d8814894c2626298dfca7aa0566c2dc46c15843850e3e14a3e05613ae9ef9fd08077042931e2fe552057f9c1bee6b69 > commons-io-2.17.0-src.zip=88418d86d8a1adbadaa4d6e66180b05e07e47ec8c6865597a0b8191481779787ce82880dbad2e1935f528d1827d36c888a374d4edd0b526f092237a58134193f > commons-io-2.17.0-test-sources.jar=ebb92dcbbdfa70baa0c67c017dad5794fd03e3893899b5d17bcfe24195f67ac7b55adfb608bb7b4c1990f6a272ec155eb45589e34d92a82a71c1a1af1adc6764 > commons-io-2.17.0-tests.jar=862218144e78833dc443468fc518d76144df38a0172d5a3824641434c203ff740628bf3d67c3d5f3451519992d5e82c9ac6422a0bc02075e2f95942f9d654263 > commons-io_commons-io-2.17.0.spdx.json=03468e53ecc370cc9e3c6bf2de51388310083d723b88626b918bf5f700f560c8a721a88e0395c34dfda1a2dce9eb8a6751483110f54b046c131b770275a85530 > > I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy > -P jacoco -P japicmp clean package site deploy' using: > > openjdk version "17.0.12" 2024-07-16 > OpenJDK Runtime Environment Homebrew (build 17.0.12+0) > OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing) > > Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > Maven home: /usr/local/Cellar/maven/3.9.9/libexec > Java version: 17.0.12, vendor: Homebrew, runtime: > /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac" > > Darwin gdg-mac-mini.local 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul > 29 21:13:00 PDT 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64 > > Details of changes since 2.16.1 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/io/2.17.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/io/2.17.0-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/io/2.17.0-RC1/site/index.html > (note some *relative* links are broken and the 2.17.0 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 2.16.1): > > https://dist.apache.org/repos/dist/dev/commons/io/2.17.0-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/io/2.17.0-RC1/site/rat-report.html > > KEYS: > https://downloads.apache.org/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) > > The 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. > > 1a) Cl
[beanutils] any suggestions towards v2
Hi, Do you have any suggestions for something I could look at to help get beanutils ready for v2? Meanwhile, I've been looking at improving test coverage of BeanComparator and I've simplified the internal natural order comparator - PR incoming Steve
Re: [beanutils] any suggestions towards v2
There are two threads on this list, one for the custom map, one for the Java platform. Gary On Mon, Sep 16, 2024, 4:34 PM Steve Bosman wrote: > Hi, > > Do you have any suggestions for something I could look at to help get > beanutils ready for v2? > > Meanwhile, I've been looking at improving test coverage of BeanComparator > and I've simplified the internal natural order comparator - PR incoming > > Steve >
Re: [beanutils] Java plaform for 2.0
I think that for now I am leaning towards staying on Java 8. Gary On Sat, Sep 14, 2024, 3:42 AM Xeno Amess wrote: > for 90%+ normal user each version under which spring using be OK > > From: Richard Zowalla > Sent: Saturday, September 14, 2024 12:59:15 PM > To: Commons Developers List > Subject: Re: [beanutils] Java plaform for 2.0 > > My 2 cents are: BeanUtils is often used in the EE ecosystem EE 9.1 targets > 8/11, EE 10 targets 11/17, EE 11 targets 17 or higher. > > People are still doing the EE8 to 9.1/10 move (thanks to the name change). > So perhaps 11 or 17 would be a good fit for a baseline version. > > Gruß > Richard > > Am 14. September 2024 00:00:48 MESZ schrieb sebb : > >On Fri, 13 Sept 2024 at 22:01, Gary Gregory > wrote: > >> > >> The age does not really matter Elric, it's the percentage of people > using a > >> platform. See the links in my previous email. I think the highest we > can go > >> is 17, but that's just me. > > > >According to the 3rd link, Java version usage in 2024 is > > > >7 - 0.2% > >8 - 28.8% > >11 - 32.9% > >17 - 35.4% > >21 - 1.4% > > > >Here is the list showing the percentages that will no longer be > >supported by choosing a particular version: > > > >7 - 0% > >8 - 0.2% > >11 - 29% > >17 - 61.9% > >21 - 97.3% > > > >Bigger is definitely not better here. > > > >> Gary > >> > >> On Fri, Sep 13, 2024, 4:11 PM Elric wrote: > >> > >> > On 12/09/2024 19:21, Gary D. Gregory wrote: > >> > > Hi All, > >> > > > >> > > Any thoughts on the minimum Java platform requirement for 2.0? > >> > > > >> > > Options are (IMO): 8, 11, 17, or 21. > >> > > >> > I have no vote, but I would go for 21. This will likely be a decision > >> > that will have an impact for a long time. 21 is 1 year old, 17 is 3 > >> > years old, 11 is already already 6 years old, and 8 is over 10 years > old. > >> > > >> > People can continue to use 1.x if they are stuck on ancient Java > >> > versions, but there should be no need to for any major release of any > >> > commons project to stick to older versions. > >> > > >> > - > >> > 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: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap
Related: https://issues.apache.org/jira/browse/COLLECTIONS-700 Gary On Sat, Sep 14, 2024, 10:16 AM Xeno Amess wrote: > IMO I think it ok...so Gary which part do you feel unsafe in it ？I must > admit I am not that familiar to lawyer things.. > > From: Melloware Inc > Sent: Saturday, September 14, 2024 9:18:08 PM > To: Commons Developers List > Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap > > Well in my PR the license in the file says this. > > Written by Doug Lea with assistance from members of JCP JSR-166 > Expert Group and released to the public domain, as explained at > @see http://creativecommons.org/licenses/publicdomain";>Creative > Commons > > it says its public domain. > > On Sat, Sep 14, 2024 at 9:01 AM Xeno Amess wrote: > > > why not write an email to lea ..maybe he be so kind that would be glad to > > offer one mit-like license copy of that class > > > > From: Melloware Inc > > Sent: Saturday, September 14, 2024 8:32:38 PM > > To: Commons Developers List > > Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap > > > > I submitted this PR years ago using ConcurrentWeakKeyHashMap from Doug > Lea > > and the Netty team but Gary had concerns from legal about being able to > use > > it. > > > > PR is here: https://github.com/apache/commons-beanutils/pull/56 > > > > On Sat, Sep 14, 2024 at 7:22 AM Xeno Amess wrote: > > > > > I thought old d-lea bro have a concurrent weak hashmap implement > > > somewhere...why not just ask him > > > after all nobody here more expert than him in this area > > > > > > From: Niall Pemberton > > > Sent: Saturday, September 14, 2024 1:46:32 PM > > > To: Commons Developers List > > > Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap > > > > > > On Thu, 12 Sep 2024 at 19:59, Gary D. Gregory > > wrote: > > > > > > > Hi All, > > > > > > > > For the upcoming 2.0.0-M1, I plan on replacing the custom > > WeakFastHashMap > > > > with the stock ConcurrentHashMap. > > > > > > > > If you think this is a bad idea, please tell us why. > > > > > > > > > It’s a good idea for the “fast” part, but the “weak” aspect also needs > to > > > be retained - so in principle yes, but the implementation detail > matters. > > > > > > BeanUtils caused memory issues in multiple ClassLoader environments > (e.g. > > > WebApp containers) because of strong references to classes prevented > them > > > from being garbage collected if the app was reloaded/restarted. So this > > > weak map was introduced to resolve that issue. > > > > > > Niall > > > > > > > > > > > > > > Gary > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > > > > -- > > == > > Melloware > > melloware...@gmail.com > > http://melloware.com > > == > > > > > -- > == > Melloware > melloware...@gmail.com > http://melloware.com > == >
Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap
Which points to: https://issues.apache.org/jira/browse/BEANUTILS-509 Gary On Mon, Sep 16, 2024, 5:24 PM Gary Gregory wrote: > Related: https://issues.apache.org/jira/browse/COLLECTIONS-700 > > Gary > > On Sat, Sep 14, 2024, 10:16 AM Xeno Amess wrote: > >> IMO I think it ok...so Gary which part do you feel unsafe in it ？I must >> admit I am not that familiar to lawyer things.. >> >> From: Melloware Inc >> Sent: Saturday, September 14, 2024 9:18:08 PM >> To: Commons Developers List >> Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap >> >> Well in my PR the license in the file says this. >> >> Written by Doug Lea with assistance from members of JCP JSR-166 >> Expert Group and released to the public domain, as explained at >> @see http://creativecommons.org/licenses/publicdomain";>Creative >> Commons >> >> it says its public domain. >> >> On Sat, Sep 14, 2024 at 9:01 AM Xeno Amess wrote: >> >> > why not write an email to lea ..maybe he be so kind that would be glad >> to >> > offer one mit-like license copy of that class >> > >> > From: Melloware Inc >> > Sent: Saturday, September 14, 2024 8:32:38 PM >> > To: Commons Developers List >> > Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap >> > >> > I submitted this PR years ago using ConcurrentWeakKeyHashMap from Doug >> Lea >> > and the Netty team but Gary had concerns from legal about being able to >> use >> > it. >> > >> > PR is here: https://github.com/apache/commons-beanutils/pull/56 >> > >> > On Sat, Sep 14, 2024 at 7:22 AM Xeno Amess wrote: >> > >> > > I thought old d-lea bro have a concurrent weak hashmap implement >> > > somewhere...why not just ask him >> > > after all nobody here more expert than him in this area >> > > >> > > From: Niall Pemberton >> > > Sent: Saturday, September 14, 2024 1:46:32 PM >> > > To: Commons Developers List >> > > Subject: Re: [beanutils] For 2.0, WeakFastHashMap vs ConcurrentHashMap >> > > >> > > On Thu, 12 Sep 2024 at 19:59, Gary D. Gregory >> > wrote: >> > > >> > > > Hi All, >> > > > >> > > > For the upcoming 2.0.0-M1, I plan on replacing the custom >> > WeakFastHashMap >> > > > with the stock ConcurrentHashMap. >> > > > >> > > > If you think this is a bad idea, please tell us why. >> > > >> > > >> > > It’s a good idea for the “fast” part, but the “weak” aspect also >> needs to >> > > be retained - so in principle yes, but the implementation detail >> matters. >> > > >> > > BeanUtils caused memory issues in multiple ClassLoader environments >> (e.g. >> > > WebApp containers) because of strong references to classes prevented >> them >> > > from being garbage collected if the app was reloaded/restarted. So >> this >> > > weak map was introduced to resolve that issue. >> > > >> > > Niall >> > > >> > > >> > > > >> > > > Gary >> > > > >> > > > >> - >> > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> > > > For additional commands, e-mail: dev-h...@commons.apache.org >> > > > >> > > > >> > > >> > >> > >> > -- >> > == >> > Melloware >> > melloware...@gmail.com >> > http://melloware.com >> > == >> > >> >> >> -- >> == >> Melloware >> melloware...@gmail.com >> http://melloware.com >> == >> >
