Hi,
since we’re getting more and more requests about the deprecation of
RandomStringUtils, I’m thinking about releasing the current state of the master
branch as 3.6.1. I may have time to push an RC sometime this week. So if you
have some fixes you want to include, please do so now.
Regards,
Le 5 sept. 2017 05:40, "Ralph Goers" a écrit :
> On Sep 4, 2017, at 2:24 PM, Romain Manni-Bucau
wrote:
>
> Le 4 sept. 2017 20:44, "Matt Sicker" a écrit :
>
> You don't duplicate any logging config. You can use both slf4j-api
> On Sep 4, 2017, at 2:24 PM, Romain Manni-Bucau wrote:
>
> Le 4 sept. 2017 20:44, "Matt Sicker" a écrit :
>
> You don't duplicate any logging config. You can use both slf4j-api and
> log4j-api with either logback or log4j2.
>
>
> Except you dont
Le 4 sept. 2017 20:44, "Matt Sicker" a écrit :
You don't duplicate any logging config. You can use both slf4j-api and
log4j-api with either logback or log4j2.
Except you dont always have the choice with 2 apis. It also messes up
logging lifecycle and setup which needs 2
You don't duplicate any logging config. You can use both slf4j-api and
log4j-api with either logback or log4j2.
On 4 September 2017 at 00:08, Romain Manni-Bucau
wrote:
> If you ignore the container point - which for me is already blocking - you
> have 2 issues with
On Aug 31, 2017 23:41, "Benedikt Ritter" wrote:
Hi again,
> Am 31.08.2017 um 01:38 schrieb sebb :
>
> On 30 August 2017 at 20:11, Benedikt Ritter wrote:
>> Hi,
>>
>> looking through the JavaDoc comments in the Visitor interface, it
Hi All,
I would live to see a release for VFS so I can pickup some bug fixes.
If any one wants to RM, great, otherwise I will have to put that on my
TO-DO list.
If you want to perform changes, now is the time. The sooner the better.
Gary
Hi.
On Mon, 4 Sep 2017 11:41:55 +0200, Emmanuel Bourg wrote:
Le 2/09/2017 à 00:50, Gilles a écrit :
Because of "Commons" rules, it is not "equivalent": There was
a long thread concluding that all modules must be released
_together_, and with the same top-level package name and version
number.
Le 2/09/2017 à 00:50, Gilles a écrit :
> Because of "Commons" rules, it is not "equivalent": There was
> a long thread concluding that all modules must be released
> _together_, and with the same top-level package name and version
> number.
True, but I don't see this as an issue.
> I think