[VOTE] Release Commons Collections 4.1 Based on RC1

Hi all, we have accumulated enough changes since the last 4.0 release as well as we need to provide a fix for the known remote code exploit via java de-serialization. Therefore, I would like to start a vote to release Commons Collections 4.1 based on RC1. Note: The fix for the security related

Re: [VOTE] Release Validator 1.5.0 based on RC1

On 11/19/2015 10:48 AM, sebb wrote: > It's probably about time to release VALIDATOR. > There have been quite a few improvements and fixes since the last version. > > == > > Validator 1.5.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/validator/ (svn >

Re: Commons NoSQL

OGM could work for log4j since we have known objects to marshall. I'll have to study it and see if there is underlying API as generally usefull as JDBC. Gary On Nov 22, 2015 7:22 PM, "Yair Zaslavsky" wrote: > Hi Gary, I'm kinda n00b and really don't participate in the

Re: Proposed fluent string utils

On Nov 22, 2015 7:31 PM, "Henri Yandell" wrote: > > My suggestion would be to add a link to teh Commons Lang website to Micha's > repo and see how successful it is (i.e. if successful, I'd expect to see > users contributing other Lang related fluent APIs to it). > > I'd

Re: [VOTE] Release NET 3.4 based on RC2 - resend with corrected tag

On 11/22/2015 04:58 PM, sebb wrote: > It's probably about time to release NET. > There have been quite a few improvements and fixes since the last version. > > [This is a repeat of the original mail, but using a tag that actually > exists this time] > > == > > Net 3.4 RC2 is available for

Re: Proposed fluent string utils

My suggestion would be to add a link to teh Commons Lang website to Micha's repo and see how successful it is (i.e. if successful, I'd expect to see users contributing other Lang related fluent APIs to it). I'd suggest renaming to fluengLang :) On Mon, Nov 16, 2015 at 11:50 AM, Benedikt Ritter

Commons NoSQL

Any thoughts on creating a JDBC for NoSQL? Including modules for MongoDb and CouchDb for example. Over at Log4j 2, we have a mini logging oriented framework for NoSQL. The upshot would be to replace Log4j's NoSQL support with Commons NoSQL. Gary

Re: Commons NoSQL

Hi Gary, I'm kinda n00b and really don't participate in the group , but isnt' there a project that is led by Emanuel Brenard about? http://hibernate.org/ogm/ Is there going to be an adapter from OGM to your suggestion? How will you cope with the fact that there are several paradigms for no SQL?

Re: [JXPATH] Java Version

I'm fine with Java 7, since Java 6 has already reached EOL. 2015-11-21 19:48 GMT+01:00 Gary Gregory : > I'd go with Java 7. > > Gary > On Nov 21, 2015 3:50 AM, "Benedikt Ritter" wrote: > > > Hi, > > > > any preference on which Java Version JXPath 1.4

Re: [RESULT] [VOTE] Accept Naomi

Folks, I take it from our collective lack of movement, that we are voting no, and just not willing to say it. If that is the case, we should have the courtesy to say no, and at least give closure. dave On 11/08/2015 02:14 PM, Dave Brosius wrote: I have already merged the changes into

Re: [JXPATH] Java Version

As has java 7 reached end of life. On 11/22/2015 09:06 AM, Benedikt Ritter wrote: I'm fine with Java 7, since Java 6 has already reached EOL. 2015-11-21 19:48 GMT+01:00 Gary Gregory : I'd go with Java 7. Gary On Nov 21, 2015 3:50 AM, "Benedikt Ritter"

Re: [JXPATH] Java Version

Java 7 seems OK to me, though if the code builds and test OK with Java 1.6, why not leave it at that? Just because Java 1.6 is EOL does not mean that Java 1.6-compatible code will stop working. So long as the Java runtime used to run the code is updated to a currently supported version of Java,

Re: [JXPATH] Java Version

On Sun, Nov 22, 2015 at 6:20 AM, Dave Brosius wrote: > As has java 7 reached end of life. FYI: I think IBM still supports their Java 7 IIRC Gayr > > > On 11/22/2015 09:06 AM, Benedikt Ritter wrote: > >> I'm fine with Java 7, since Java 6 has already reached EOL. >> >>

Re: [JXPATH] Java Version

Okay, so we go with Java 8? Doesn't feel like it has reached enough market penetration yet. But I don't know numbers about that. 2015-11-22 15:20 GMT+01:00 Dave Brosius : > As has java 7 reached end of life. > > On 11/22/2015 09:06 AM, Benedikt Ritter wrote: > >> I'm fine

Re: [JXPATH] Java Version

Unfortunately Android still uses Java 7, if you want Android developers to be able to use the library then I think you should target 7. On Sun, Nov 22, 2015 at 7:12 AM, Benedikt Ritter wrote: > Okay, so we go with Java 8? Doesn't feel like it has reached enough market >

Re: [RESULT] [VOTE] Accept Naomi

The person who called the VOTE should tally it up and report here. Gary On Sun, Nov 22, 2015 at 6:14 AM, Dave Brosius wrote: > Folks, > > I take it from our collective lack of movement, that we are voting no, and > just not willing to say it. If that is the case, we should

[CANCELLED][VOTE] Release NET 3.4 based on RC2

I overlooked a file when creating RC1, so I abandoned that, but I did not yet delete the tag. Unfortunately when I created the tag for RC2, it was created under validator: https://svn.apache.org/repos/asf/commons/proper/validator/tags/NET_3_4_RC2/ The NET tag

[VOTE] Release NET 3.4 based on RC2 - resend with corrected tag

It's probably about time to release NET. There have been quite a few improvements and fixes since the last version. [This is a repeat of the original mail, but using a tag that actually exists this time] == Net 3.4 RC2 is available for review here:

Re: [VOTE] Release Validator 1.5.0 based on RC1

Oh, I forgot to say that the build fails with Java 8 due to the usual Javadoc failures but it was fine with my main platform: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00) Maven home: E:\Java\apache-maven-3.3.9\bin\.. Java version: 1.7.0_79, vendor:

Re: [VOTE] Release Validator 1.5.0 based on RC1

+1 >From src zip, builds OK, reports OK (Clirr, RAT), ASC OK, SHA1 OK, MD5 OK. We should really fix some of the FindBugs but there are no blockers. Gary On Thu, Nov 19, 2015 at 1:48 AM, sebb wrote: > It's probably about time to release VALIDATOR. > There have been quite a

Re: [RESULT] [VOTE] Accept Naomi

On Sun, Nov 22, 2015 at 9:51 AM, Phil Steitz wrote: > On 11/22/15 8:47 AM, Gary Gregory wrote: > > The person who called the VOTE should tally it up and report here. > > I did tally the VOTE. We had three -1 PMC Votes. I asked the -1s > to reconsider and they did not

Re: [JXPATH] Java Version

If you pay Oracle for long term support you still get updates for Java 7. This means that there will be some people (like me at work :() which have to stick to Java 7 for some time. Am 22.11.2015 um 16:44 schrieb Gary Gregory: On Sun, Nov 22, 2015 at 6:20 AM, Dave Brosius

Re: [VOTE] Release NET 3.4 based on RC2 - resend with corrected tag

Build works fine for me with Java 1.5 and Java 1.8 on Windows 10. Artifacts and site look good. So +1. Interestingly, when I build the site locally my clirr report shows 12 errors. In addition to the 3 errors about methods added to an interface, I also get a bunch of errors about public methods

Re: [RESULT] [VOTE] Accept Naomi

On 11/22/15 8:47 AM, Gary Gregory wrote: > The person who called the VOTE should tally it up and report here. I did tally the VOTE. We had three -1 PMC Votes. I asked the -1s to reconsider and they did not change their votes. Technically, we could call it a pass and push forward, but I was not

Re: [VOTE] Release NET 3.4 based on RC2 - resend with corrected tag

+1 >From src zip: builds OK, reports OK, ASC, MD5, SHA1 OK. Tested with Java 8 and 7: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00) Maven home: E:\Java\apache-maven-3.3.9\bin\.. Java version: 1.8.0_65, vendor: Oracle Corporation Java home: C:\Program