[compress] (Internal)LZWInputStream

Hi I'm trying to bring together two separate discussions from two different [VOTE]-threads. It seems as if I should cancel the RC2 vote and before I rush another RC maybe we can get consensus on what to do. * my experiments show that moving the LZWInputStream class hasn't got as big an impact

Re: [RDF] Local Scope and BlankNode internalIdentifier (was: github Commons RDF vs. Apache Commons Sandbox RDF)

Hi Andy, This analogy might help (or not): > > There is a table with 4 metal spheres on it in a line across it. Each > sphere is exactly kind of material, the same mass, the same colour and the > same shininess. You can ask "is that sphere the same as that other one?" > by pointing to two of th

[DBCP] Getting ready to roll 2.1

I am about ready (at last) to start rolling RCs for DBCP 2.1. I just opened an issue [1] that I am on the fence about and would like feedback on. I am not sure, actually, that it is an improvement to force initial requests to queue waiting for the pool to be pre-filled (what the patch now does).

Re: Anyone interested in regular expressions, again?

I like the idea. I've run into this problem before. The library I've been most familiar with is re2 for C++, but a popular Java version would be great. On Sat, Jan 31, 2015 at 11:27 AM, Phil Steitz wrote: > On 1/31/15 8:58 AM, Benson Margulies wrote: > > So, onc

Re: Anyone interested in regular expressions, again?

On 1/31/15 8:58 AM, Benson Margulies wrote: > So, once upon a time, there was a regex library here. It was retired, > presumably on the grounds that it was rendered obsolete by the JRE's > native support. > > However, the JRE's regular expressions have a pretty severe problem; > they have unbounded

Re: [RDF] Local Scope and BlankNode internalIdentifier (was: github Commons RDF vs. Apache Commons Sandbox RDF)

Hi Peter, Of your usecases the only one which might be an argument for exposing an blank-node id is: 1. The same document parsed using the same parser implementation into > the same graph may generate BlankNode objects that are .equals and if > they are .equals the .hashCode must be the same. >

Re: [collections] COLLECTIONS-551

Hi, I've sent a pull request containing CollectionUtils refactor for review (COLLECTIONS-551). Since the next release version is 4.1, I'm wondering if methods that were deprecated which are tagged with "@since 4.1" shouldn't be promptly removed from CollectionUtils. Gonçalo On Sat, Jan 31, 2

[GitHub] commons-collections pull request: Collections 551

GitHub user gonmarques opened a pull request: https://github.com/apache/commons-collections/pull/8 Collections 551 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gonmarques/commons-collections COLLECTIONS-551 Alternatively you

Re: [RDF] Local Scope and BlankNode internalIdentifier (was: github Commons RDF vs. Apache Commons Sandbox RDF)

Hi Stian, > By keeping the "internalIdentifier" property, an application is able > to talk about an existing blankNode without having to keep track of > earlier BlankNode instances (e.g. not needing their own > Map). > By application I assume you mean an implementation of the API. Even without ex

Re: Anyone interested in regular expressions, again?

We are still relying on a kind of "Apache ORO" in OFBiz, exactly jakarta-oro-2.0.8.jar http://jakarta.apache.org/site/news/news-2010-q3.html#20100901.2 While working on https://issues.apache.org/jira/browse/OFBIZ-5395 (out of scope here) I noted the same reference than Bruno for the benchmark.

Re: Anyone interested in regular expressions, again?

On Sat, Jan 31, 2015 at 12:22 PM, Bruno P. Kinoshita wrote: > Hi Benson! > I wouldn't be able to help at the moment, but some years ago I had a > performance issue in a Nutch crawler with regexes [1] and found about this > other library that you mentioned I think. Are you talking about ORO? Yes

Re: Anyone interested in regular expressions, again?

Hi Benson! I wouldn't be able to help at the moment, but some years ago I had a performance issue in a Nutch crawler with regexes [1] and found about this other library that you mentioned I think. Are you talking about ORO?  I ended up changing the regex and never had a chance to play with ORO or

Anyone interested in regular expressions, again?

So, once upon a time, there was a regex library here. It was retired, presumably on the grounds that it was rendered obsolete by the JRE's native support. However, the JRE's regular expressions have a pretty severe problem; they have unbounded (or at least, very, very, bad) execution time for some

Re: [VOTE] Release Compress 1.10 based on RC2

On 31 January 2015 at 11:41, Stefan Bodewig wrote: > On 2015-01-31, sebb wrote: > >> On 31 January 2015 at 09:03, Stefan Bodewig wrote: >>> On 2015-01-31, sebb wrote: > Given that the protected fields were in a class marked as internal, it seems arguable that users should not have refer

Re: [VOTE] Release Compress 1.10 based on RC2

On 2015-01-31, sebb wrote: > On 31 January 2015 at 09:03, Stefan Bodewig wrote: >> On 2015-01-31, sebb wrote: >>> Given that the protected fields were in a class marked as internal, it >>> seems arguable that users should not have referred to any of the items >>> in it. >>> Therefore we could po

Re: [VOTE] Release Compress 1.10 based on RC2

On 31 January 2015 at 09:03, Stefan Bodewig wrote: > On 2015-01-31, sebb wrote: > >> Given that the protected fields were in a class marked as internal, it >> seems arguable that users should not have referred to any of the items >> in it. >> Therefore we could potentially make all the mutable pro

Re: [collections] COLLECTIONS-551

Hi, Just to let you know I'm working on this. Gonçalo On Thu, Jan 29, 2015 at 9:07 PM, Thomas Neidhart wrote: > On 01/29/2015 11:57 AM, Gonçalo Marques wrote: > > Hello, > > > > I'm creating this thread in order to discuss issue COLLECTIONS-551. > > > > I don't know the deprecation policies o

Re: [VOTE] Release Compress 1.10 Based on RC1

On 2015-01-30, Benedikt Ritter wrote: > What will happen if a client has overwritten a method from > InternalLZWInputStream? My example already did, close is implemented in InternalLZWInputStream. I just extended the example to also override setClearCode and it still works. Stefan

Re: [VOTE] Release Compress 1.10 based on RC2

On 2015-01-31, sebb wrote: > Given that the protected fields were in a class marked as internal, it > seems arguable that users should not have referred to any of the items > in it. > Therefore we could potentially make all the mutable protected fields > private (and add protected getters). Even