Hello all,
Whichever names we pick if we accept the contribution, I think it is best
to look at the method names in context, not standalone.
For example, you would "say":
stopWatch.accept(x -> ...)
and so on.
I find it simpler to match the new names with the delegate but YMMV ;-)
All the name
I think this is a useful addition, but I wonder if these new APIs are
misnamed: StopWatch::test doesn't actually test, nor does StopWatch::accept
consume. Instead, these all wrap lambdas in a timed version of the same
type. (There's probably some lambda calculus terminology for this.)
I'd propose
Thank you for the details Alex.
WRT SBOM generation, I think this will be become more important as
time goes on, so anything we can do to improve the ecosystem will benefit
us all IMO.
Gary
On Sat, Aug 17, 2024, 11:03 AM Alex Herbert
wrote:
> Thanks Gary, see notes below...
>
> On Sat, 17 Aug
Thanks Gary, see notes below...
On Sat, 17 Aug 2024 at 15:12, Gary Gregory wrote:
>
> +1
>
> - I tested the src zip files.
> - ASC OK
> - SHA512 OK
> - default Maven build OK
> - Odd output:
>
> [WARNING]
> /Users/garydgregory/rc/stats/commons-statistics-1.1-src/commons-statistics-descriptive/sr
+1
- I tested the src zip files.
- ASC OK
- SHA512 OK
- default Maven build OK
- Odd output:
[WARNING]
/Users/garydgregory/rc/stats/commons-statistics-1.1-src/commons-statistics-descriptive/src/main/java/org/apache/commons/statistics/descriptive/Statistics.java:[215,25]
compose(java.util.functio
Gary,
I know your time is limited. This is not a comment on you personally, I
know how much time you put in Apache Commons. But it is a comment on Apache
Commons in general and their strict release and release processes and
limited number of people who can do releases.
As I mentioned before some
Why not help resolve one of the last issues, if not the last for 2.0 then:
pulling up the "2" type(s?) into their super types (I think there is only
one). The last time I tried, some tests failed.
Gary
On Sat, Aug 17, 2024, 9:38 AM Melloware Inc wrote:
> Jia,
>
> Sadly it's the same reason I fo
Jia,
Sadly it's the same reason I forked it and released it to Maven Central.
My client needed to get rid of commons collections3 and BeanUtils 1.9.4 is
tied to it. We wanted to only have Commons Collections4 in all our code.
https://github.com/melloware/commons-beanutils2
com.melloware
c
Hello Jia,
A release will happen only if required to fix a bug that hampers development.
Is there a fix/change in the 1.X branch you need that is not in 1.9.4?
See changes.xml
Gary
On 2024/08/17 09:51:55 吾名 wrote:
> dear Commons maintainers,
>
>
> Thank you for your greatr work in Apache Com
dear Commons maintainers,
Thank you for your greatr work in Apache Commons. It helps a lot.
I noticed the beanutils 2.0 is being developed. And the recent release of
Apache Commons Beanutils was 1.9.4, which is released in 2019. Do you have any
plan on a new release of beanutils 1.x before 2.
10 matches
Mail list logo