We have fixed quite a few bugs and added some significant enhancements since
Apache Commons DbUtils 1.7 was released, so I would like to release Apache
Commons DbUtils 1.8.
Apache Commons DbUtils 1.8 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/dbutils/1.8
Thanks for adding that version. I’ll work on marking tickets that are in this
release.
There have been a few API additions, requiring Java 1.7 instead of 1.6, and the
addition of a new annotation. It feels like enough to go with 1.8 rather than
1.7.1, but I’m open to stronger opinions.
> On J
If you guys can’t sort it out by tomorrow evening, I can roll
1.8.
-Rob
> On Jan 4, 2020, at 6:43 PM, Gary Gregory wrote:
>
> I added 1.8 but the it could be changed to 1.7.1 if no new API is added.
>
> Gary
>
>> On Sat, Jan 4, 2020, 18:40 Carl Hall wrote:
>>
>> I don’t seem to have the ri
I added 1.8 but the it could be changed to 1.7.1 if no new API is added.
Gary
On Sat, Jan 4, 2020, 18:40 Carl Hall wrote:
> I don’t seem to have the right permissions to create a release in Jira for
> DbUtils[1]. Could someone grant me those permissions, or create a 1.8
> release, please? Than
I don’t seem to have the right permissions to create a release in Jira for
DbUtils[1]. Could someone grant me those permissions, or create a 1.8 release,
please? Thanks!
https://jira.apache.org/jira/projects/DBUTILS?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=no-f
Forwarding to ML.
Gilles
P.S. Please don't send to me directly when the post is meant for
the list, as otherwise hitting "Reply" will move the conversation
off-list...
-- Forwarded message -
De : Gilles Sadowski
Date: sam. 4 janv. 2020 à 19:54
Subject: Re: [Geometry] Class "Equi
Gilles,
I removed the Equivalency interface and pushed the changes to my current PR,
along with some changes related to the shape-generation classes (GEOMETRY-83).
In regard to renaming "eq" to "equals", I personally prefer "eq" (short for
"equivalent") to make it more distinct from "equals". T
The Apache Commons Codec package contains simple encoder and decoders for
various formats such as Base64 and Hexadecimal. In addition to these
widely used encoders and decoders, the codec package also maintains a
collection of phonetic encoding utilities.
Feature and fix release.
Changes in this
On 2020-01-04, Gary Gregory wrote:
> Java has a service leader mechanism for that. No sense in duplicating it.
Compress already supports that, and IIRC you've added that yourself :-)
Stefan
-
To unsubscribe, e-mail: dev-unsubsc
Java has a service leader mechanism for that. No sense in duplicating it.
If that means updating to Java 8, then so be it.
Gary
On Sat, Jan 4, 2020, 07:58 Emmanuel Bourg wrote:
> Le 04/01/2020 à 12:19, Stefan Bodewig a écrit :
>
> > This won't work as CompressorStreamFactory depends on the pack
Le 04/01/2020 à 12:19, Stefan Bodewig a écrit :
> This won't work as CompressorStreamFactory depends on the package.
Maybe some reflection could address that?
> https://github.com/pack200/pack200 looks pretty public to me :-)
I've just pushed a raw extraction of the OpenJDK code with its histo
On Sat, 4 Jan 2020 at 11:19, Stefan Bodewig wrote:
> On 2020-01-04, Emmanuel Bourg wrote:
>
> > Le 02/01/2020 à 11:06, Stefan Bodewig a écrit :
>
> >> Any other ideas?
>
> > The removal of pack200 isn't an issue for the upcoming release yet since
> > we still target Java 7. For now this is just a
Hello.
2020-01-04 6:10 UTC+01:00, Matt Juntunen :
> Gilles,
>
> I took another look at the code and it turns out we can easily remove the
> entire Equivalency interface and just use methods of the form "eq(T,
> DoublePrecisionContext)", exactly the same way that the VectorXD classes do
> it now. T
On 2020-01-04, Emmanuel Bourg wrote:
> Le 02/01/2020 à 11:06, Stefan Bodewig a écrit :
>> Any other ideas?
> The removal of pack200 isn't an issue for the upcoming release yet since
> we still target Java 7. For now this is just an issue with the CI using
> Java 14+. Maybe we can deal with this
Le 02/01/2020 à 11:06, Stefan Bodewig a écrit :
> Any other ideas?
The removal of pack200 isn't an issue for the upcoming release yet since
we still target Java 7. For now this is just an issue with the CI using
Java 14+. Maybe we can deal with this by using a Maven profile excluding
the pack200
15 matches
Mail list logo