Gary,
I compiled the 64-bit Windows build on my Mac and tested it in a
Windows VM. It was fairly straightforward with mingw. I still need
to cross-compile the Linux builds, but I'm cautiously optimistic that
they will be trivial compared to the Windows cross compilation.
Everything is easier on
Hello.
Le jeu. 16 juil. 2020 à 06:08, Matt Juntunen
a écrit :
>
> We have been working hard to prepare Apache Commons Geometry for an initial
> release, so I would like to release Apache Commons Geometry (full
> distribution) 1.0-beta1.
>
> Apache Commons Geometry 1.0-beta1 RC3 is available
+1 ... Good work...keep it up :-)
Checked signatures
Checked reports,
Checked build with java 8 and java 11
All checks out
-Rob
> On Jul 16, 2020, at 12:08 AM, Matt Juntunen wrote:
>
> We have been working hard to prepare Apache Commons Geometry for an initial
> release, so I would like to
Sample use cases:
1. Perform multiple operations, some failed due to different reasons.
Return a CompositeException for the failed ones.
2. Do a validation on some input. I want to collect all different failures,
I can throw a CompositeException.
3. In some cases the exception had occurred
What is the use case for this?
On Fri, 17 Jul 2020 at 16:29, Adwait Kumar Singh
wrote:
>
> Yes Gary, something similar. However it would differ from IOExceptionList
> which creates an aggregated message of all exceptions but loses the
> stacktrace via getCause or printStackTrace.
>
> To be
Yes Gary, something similar. However it would differ from IOExceptionList
which creates an aggregated message of all exceptions but loses the
stacktrace via getCause or printStackTrace.
To be precise, this is exactly what I am taking about
Would it be like Common IO's IOExceptionList or Commons DBCP
SQLExceptionList ?
Gary
On Fri, Jul 17, 2020 at 11:01 AM Adwait Kumar Singh <
theadvaitkumarsi...@gmail.com> wrote:
> To be more specific, I meant a util function in ExceptionUtils. Like this,
>
>
To be more specific, I meant a util function in ExceptionUtils. Like this,
ExceptionUtils.createCompositeException(String overallErrorMessage,
Throwable... throwables)
This would return a CompositeException which would contain all the
Throwables and whose getCause() and printStackTrace() methods
Thanks Gary!
> On Jul 17, 2020, at 9:52 AM, Gary Gregory wrote:
>
> The Apache Commons Lang team has released version 3.11.
>
> This document contains the release notes for the 3.11 version of Apache
> Commons Lang.
> Commons Lang is a set of utility functions and reusable components that
>
The Apache Commons Lang team has released version 3.11.
This document contains the release notes for the 3.11 version of Apache
Commons Lang.
Commons Lang is a set of utility functions and reusable components that
should be of use in any
Java environment.
Lang 3.9 and onwards now targets Java 8,
I agree with Gary. I know its been decided but I thought I would add
my -1.
Technology better have a compelling reason to switch and in the past we
have had:
Ant -> Maven was a big leap for convention over configuration and
dependency management
SVN -> GIT was a big leap for the
Pardon…my email threads got crossed there…a little too busy…will reply to vote
thread.
-Rob
> On Jul 17, 2020, at 9:01 AM, Rob Tompkins wrote:
>
> Yes
>
>> On Jul 17, 2020, at 7:38 AM, Matt Juntunen wrote:
>>
>> Hi Rob,
>>
>> Just to be clear, your +1 is for the commons-geometry release
Yes
> On Jul 17, 2020, at 7:38 AM, Matt Juntunen wrote:
>
> Hi Rob,
>
> Just to be clear, your +1 is for the commons-geometry release based on rc3?
>
> -Matt
>
> From: Rob Tompkins
> Sent: Thursday, July 16, 2020 11:19 PM
> To: Commons Developers List
>
Hi Rob,
Even though I am on the minus side, I am glad you brought this up for
discussion. I think it helped us better understand where we are, how we got
here, and why we want to stay.
Gary
On Fri, Jul 17, 2020 at 7:25 AM Rob Tompkins wrote:
> Very much appreciation guys for the thoughtful
Hi Commons devs,
Use case : Ability to a single exceptions with multiple causes. This
required in validation or initialization scenarios for example when I want
to Validation/Initialization failures for multiple reasons and each reason
having a unique cause.
RxJava provides something similar
Hi Rob,
Just to be clear, your +1 is for the commons-geometry release based on rc3?
-Matt
From: Rob Tompkins
Sent: Thursday, July 16, 2020 11:19 PM
To: Commons Developers List
Subject: Re: [all] on automating signature validation (Was: Re: [VOTE] Release
Very much appreciation guys for the thoughtful words and opinions here. Sounds
like we’re sticking with Maven. :-)
I hope everyone is doing well these days.
Cheers,
-Rob
> On Jul 17, 2020, at 4:24 AM, Thomas Vandahl wrote:
>
> On 17.07.20 10:13, Claude Warren wrote:
>> -1 from me. I have a
Hi Benedikt, **
*Per the JDK 15 schedule, we are in Rampdown Phase Two* *[1]*
Per the JDK Release Process [2] we now turn our focus to *P1 and P2
bugs*, which can be fixed with approval [3].
Late enhancements are still possible, with approval [4], but the bar is
now extraordinarily high.
On 17.07.20 10:13, Claude Warren wrote:
> -1 from me. I have a philosophical objection.
Same here: -1
> Much like HTTP's mod_rewrite[1] gradle's greatest strength is that it
> allows the developer to do so much in so many ways. But its greatest
> weakness is that it allows the developer to do
-1 from me. I have a philosophical objection.
Much like HTTP's mod_rewrite[1] gradle's greatest strength is that it
allows the developer to do so much in so many ways. But its greatest
weakness is that it allows the developer to do so much in so many ways.
My experience with Ant and Gradle is
-0.5 from me, to have suffered from projects having done it I think it
wouldn't be sane for commons
Big advantage of gradle is to be flexible but it also means you do a one
man build, lose most of the IDE integration (even IDEA integration is not
good, you often must use gradle runner to run test
21 matches
Mail list logo
