Re: commons-io git repository write access

Hi, Pascal Schumacher schrieb am So., 6. Nov. 2016 um 10:49 Uhr: > Are you sure this works for commons-io? > > I tried a configuration similar to commons-lang, but get: > > "remote: You are not authorized to edit this repository." > I've heart something like this from

Re: [Text,Lang] Moving code into commons-text

Hello Rob, Rob Tompkins schrieb am So., 6. Nov. 2016 um 17:20 Uhr: > Hi, > > I’ve heard of some intent to get the text functionality out of Lang in the > long term future and am thinking about starting to chip away at doing this. > It seems that minimally moving over

Re: FindBugs project announced as 'dead', blaims code rot and lack of maintainers

Looks like Bill Pugh was woken up: https://twitter.com/wpugh/status/795350364291813376 2016-11-06 19:00 GMT+01:00 Gary Gregory : > The whole post is interesting. Sounds like a fork is inevitable. So much > work though... > > Gary > > On Nov 6, 2016 9:32 AM, "Stian

Re: [TEXT] TEXT-10 A more complex Levenshtein distance

Hi Bruno,The existing array with name "d", at any given instance contains data meant for only one row in the matrix.My understanding to get the number of inserts, deletes and substitutes, we need to form the complete matrix and iterate the diagonal elements to get the values.Considering this I

RE: [crypto] package access on ivars?

Hi Gary, >> I see ivars left at the package access level. This must be an oversight, >> right? Thank you for the suggestion, I will fix it. >> We can only fix that in 2.0 and a new package. What a bummer! I'm agreed with you, the new package could also contain the recent fixes. Thank you :)

Re: [Text,Lang] Moving code into commons-text

On Sun, Nov 6, 2016 at 12:22 PM, Bruno P. Kinoshita < brunodepau...@yahoo.com.br.invalid> wrote: > Hi Rob, > > > I’ve heard of some intent to get the text functionality out of Lang in > the long > > term future and am thinking about starting to chip away at doing this. > It seems > > that

Re: [Text,Lang] Moving code into commons-text

Hi Rob, > I’ve heard of some intent to get the text functionality out of Lang in the > long > term future and am thinking about starting to chip away at doing this. It > seems > that minimally moving over “org.apache.commons.lang3.text" would be a > start. Does anyone have any thoughts about

[crypto] package access on ivars?

Hi all, I see ivars left at the package access level. This must be an oversight, right? We can only fix that in 2.0 and a new package. What a bummer! Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

Re: FindBugs project announced as 'dead', blaims code rot and lack of maintainers

The whole post is interesting. Sounds like a fork is inevitable. So much work though... Gary On Nov 6, 2016 9:32 AM, "Stian Soiland-Reyes" wrote: > See > https://mailman.cs.umd.edu/pipermail/findbugs-discuss/ > 2016-November/004321.html > > In particular the author is not

Re: FindBugs project announced as 'dead', blaims code rot and lack of maintainers

The problem is the admin/owner has left and refuses to give access to anyone else. The team has already decided to hard - fork, and is working to get set up. Anyone interested in joining is welcome. Contact me if interested. On 11/06/2016 12:32 PM, Stian Soiland-Reyes wrote: See

FindBugs project announced as 'dead', blaims code rot and lack of maintainers

See https://mailman.cs.umd.edu/pipermail/findbugs-discuss/2016-November/004321.html In particular the author is not happy about the BCEL integration: > The other major reasons for the FindBugs current bad state: > > 1) The code is very complex, has "organically grown" over a decade, is > not

[Text,Lang] Moving code into commons-text

Hi, I’ve heard of some intent to get the text functionality out of Lang in the long term future and am thinking about starting to chip away at doing this. It seems that minimally moving over “org.apache.commons.lang3.text" would be a start. Does anyone have any thoughts about what else might

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Hi, sorry, I don't want to stand in the way of the release. It is just that in the past we used to be very careful with artifacts deployed to Maven central and their compatibility. When I did alpha and beta releases for [configuration] 2.0 it was decided that these artifacts must not be published

Re: [DAEMON] Outdated parent pom

On 06/11/2016 09:07, Guillaume Ch wrote: > Hello, > > I've noticed that daemon parent pom version is 35, why not upgrading to 41 > now ? Just haven't got around to it. I've just tested it and there are no immediately obvious issues so I'll commit it shortly. Mark

Re: commons-io git repository write access

Are you sure this works for commons-io? I tried a configuration similar to commons-lang, but get: "remote: You are not authorized to edit this repository." Am 05.11.2016 um 23:54 schrieb Gary Gregory: Nothing if you are an Apache committer already, you have karma automatically. Gary On Nov

[DAEMON] Outdated parent pom

Hello, I've noticed that daemon parent pom version is 35, why not upgrading to 41 now ?