On Mon, 11 Apr 2016, Benson Margulies wrote:
A patch:
Key added in r13138
Nick
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
On Sun, 21 Feb 2016, Gary Gregory wrote:
Curious: How to you get to OpenSSL, JNI? JNA?
I know that Tomcat has done quite a bit of work around pulling in OpenSSL
in order to do SNI and ALPN. Mark Thomas gave a good talk on it at
ApacheCon last year, slides are at:
http://events.linuxfoundatio
On Sun, 22 Nov 2015, Gary Gregory wrote:
Any thoughts on creating a JDBC for NoSQL? Including modules for MongoDb
and CouchDb for example.
Isn't that what Apache Gora already provides?
Nick
-
To unsubscribe, e-mail: dev-unsub
On Fri, 30 Oct 2015, luc wrote:
In fact, pull requests are really github-specific, and we don't have a
complete integration between our Apache infrastructure and github for
Commons Math. As an example, the requests are not directly forwarded to
our mailing lists so we may miss them (and we alre
On Sat, 10 Oct 2015, Phil Steitz wrote:
On 10/8/15 8:45 AM, Nick Burch wrote:
TL;DR - There's a handful of Java mini-projects, one per file
format, each with a library and command-line tools, in and around
Apache Tika. Would Commons be a good Apache home for them?
This depends on wha
Hi All
TL;DR - There's a handful of Java mini-projects, one per file format,
each with a library and command-line tools, in and around Apache Tika.
Would Commons be a good Apache home for them?
Apache Tika, for those who don't know, is a toolkit for detecting file
types, then extracting con
On Tue, 18 Sep 2012, Thomas Neidhart wrote:
does anybody plan to go to ApacheCon 2012?
I'm not involved in math, only validator, but I'll be there :)
The Monday (5th November) is a hackathon, which should be a great chance
for commons developers (and others!) to get together to work on code /
On Sun, 4 Mar 2012, Simone Tripodi wrote:
nice contribution!
I've been one of the last committers on touching [validator] so unless
someone else is faster than me, I'll try to take care about it ASAP.
I've raised VALIDATOR-305 to track this, but I probably won't have a
chance to look at fixing
On Wed, 1 Feb 2012, Simone Tripodi wrote:
thanks for reviewing! I am personally worried to fix the findbugs errors
and break the backward compatibility, I'll ask Nick's help!
I'm not sure how serious those warnings are, and I'm pretty sure that
those problems were present in 1.3, so I think th
On Sun, 29 Jan 2012, Simone Tripodi wrote:
after the failing RC1, I open the VOTE for Apache Commons validator
1.4.0 based on RC2. Follow details:
Looks fine to me, I'm +1
My only comment is that it doesn't look like your GPG key has been signed
by anyone. I don't think that's a blocker, but
On Sun, 29 Jan 2012, Oliver Heger wrote:
Looks good now, my concerns have been addressed. The only minor nit I found
is that the ant build is not able to execute the tests. It fails with
test.main:
[echo] Running main tests ...
[java] Class not found "org.apache.commons.validator.Validat
On Sat, 28 Jan 2012, sebb wrote:
On 28 January 2012 17:46, wrote:
Author: nick
Date: Sat Jan 28 17:46:58 2012
New Revision: 1237106
URL: http://svn.apache.org/viewvc?rev=1237106&view=rev
Log:
Update the ibiblio URLs for downloading dependencies
Why not download from Maven Central?
I was a
On Sat, 28 Jan 2012, Niall Pemberton wrote:
The problem was introduced 3 weeks ago in r1227700 when ResultStatus was
changed from being an inner class to a static inner class.
http://svn.apache.org/viewvc?view=revision&revision=1227700
I've committed a deprecated, overloaded constructor for t
On Sat, 28 Jan 2012, Oliver Heger wrote:
I had problems with the ant build, there were compilation errors. I am
not sure whether I have to define the paths to dependent libraries in
build.properties. This is not mentioned in the building instructions,
and build.xml tries to download some librar
On Fri, 27 Jan 2012, Simone Tripodi wrote:
as promised time ago, I finally found the slot to rollout the
[validator] RC and I am here today to open the VOTE for Apache Commons
validator 1.4.0 based on RC1. Follow details:
Artifacts look good to me, I'm +1
Nick
---
On Tue, 10 Jan 2012, Simone Tripodi wrote:
any reason why this release has to be a beta1? With all that fixed
issues, I would expect a GA release... WDYT?
I think it's fine to be a GA release. Back when I first tried to do the
release, the plan was to do a beta first as there were quite a few
On Fri, 6 Jan 2012, Simone Tripodi wrote:
I did some work on [validator] for the release but did not get through
the issues since I'm not so familiar to [validator] so much... if you
could have a look at them, I can continue providing my help.
Looks like you've done loads, thanks!
I've applied
On Tue, 3 Jan 2012, Simone Tripodi wrote:
I can help you for cutting the RC, I'll start to have a look at
[validator] stuff tonight.
Great, thanks! The patches to fix the last vote issues are in JIRA
Nick
-
To unsubscribe, e-
On Mon, 2 Jan 2012, Raminderjeet Singh wrote:
We are using Common Validator in Apache Rave project and faced issue
related to validation of localhost URL's. Using 1.4.0-SNAPSHOT version i
am able to fix the problem but we cant release with Snapshot version
jar. What is the plan to Release 1.4.0
On Sun, 27 Nov 2011, | Erhan Bagdemir wrote:
Is there any plan or improvement for Validator project?
I was hoping to get another release out during ApacheCon, but alas I
didn't get the time. It is on my todo list, but if someone fancied helping
by working up a patch to fix the issues raised
Hi All
I've had a couple of goes at rolling a new release of Commons Validator
recently, but thus far I've been un-sucessful as there's always been a
problem with the artifacts...
I was wondering, are any current Commons Release Managers going to be at
ApacheCon in a week's time? And if so,
Hi All
Following the advice from the previous failed vote, I've rolled another RC
for Commons Validator 1.4 beta 1. As per advice, this one was generated
using Maven[1] rather than Ant. Just for a reminder, the idea of this
release is to get some wider testing of the codebase, owing to the 4.5
On Thu, 2 Jun 2011, Niall Pemberton wrote:
If you use the Maven2 build then it should all build as expected.
So it seems. I think I'll remove the release target from the ant build (so
no-one else tries it and gets bitten), then see if I can figure out how to
use the maven release plugin!
Ni
On Thu, 2 Jun 2011, Oliver Heger wrote:
About the distribution files: Shouldn't the naming be
commons-validator-1.4.0-beta1 rather than validator-1.4.0-beta1? Also
the manifest of the jar in the binary distribution does not contain all
properties typical for commons components. When I build the
Hi All
Following last week's discussions, I've rolled a RC for Commons Validator
1.4 beta 1. The idea of this release is to get some wider testing of the
codebase, owing to the 4.5 year gap since 1.3.1, before we hopefully
release 1.4 in a few weeks time.
(We believe the code is stable and r
On Sat, 28 May 2011, sebb wrote:
So IMO if we want to change the groupid or make small incompatible
changes it would be OK.
Changing the groupId without changing the package name can result in
two copies of the library on the classpath, which is much harder to
debug than a binary API change. I
On Fri, 27 May 2011, Jörg Schaible wrote:
You should not use non-ASCII characters in source code. You have no
control over the OS encoding used for anyone else that checks out the
source (Subversion has no idea about encoding) or downloads it from our
tarballs. Always use \u encoding.
Tha
On Fri, 27 May 2011, Gary Gregory wrote:
You have to call for a [vote] to be release manager IIRC.
http://commons.apache.org/releases/prepare.html indicates it can be done
with a lazy consensus, is that still correct?
Nick
On Fri, 27 May 2011, sebb wrote:
Or don''t fix the groupId until you have to change the package name for
some other reason, e.g. API breakage.
Ah, that's a pain. I'll put it back for now, as it's not the easy fix I
thought it was...
Nick
-
Hi All
I think it's been quite a while since the last commons validator release
(1.3.1 seems to date from 2006!). However, there have been quite a few bug
fixes since then, even if the refactoring into the routines package that
was the hope for 1.4 isn't quite complete.
I think it's probably
On Mon, 4 Apr 2011, Nick Burch wrote:
On Mon, 28 Mar 2011, Nick Burch wrote:
At the moment, the Email Validator considers @localhost email addresses to
be invalid, due to the Domain Validator not considering it to be valid.
Initially I thought this was wrong for all cases, so I opened
On Mon, 28 Mar 2011, Nick Burch wrote:
At the moment, the Email Validator considers @localhost email addresses
to be invalid, due to the Domain Validator not considering it to be
valid.
Initially I thought this was wrong for all cases, so I opened
VALIDATOR-292 and attached a patch that
Hi All
At the moment, the Email Validator considers @localhost email addresses to
be invalid, due to the Domain Validator not considering it to be valid.
Initially I thought this was wrong for all cases, so I opened
VALIDATOR-292 and attached a patch that fixed this. However, after a bit
mor
On Fri, 31 Oct 2008, David Durham, Jr. wrote:
Nick mentioned that commons might be a better home for this.
I thought commons might be a better home, as the project handles both csv
and xls (via poi), mapping both ways between javabeans. I think it's an
interesting idea, just maybe not quite r
On Fri, 11 Apr 2008, Rahul Akolkar wrote:
Naming wise, the ones that I can think of are me, mobile or micro. Might
be a bit broad/generic though, what do people think?
I'm fine with any of those.
OK, I've gone with "me" for now, but I'm happy to change if there's a
preference for something
On Thu, 10 Apr 2008, Rahul Akolkar wrote:
> I think we need a different name ( not [j2me] ). Please try to define a
> scope via a proposal ( see recent example:
> http://markmail.org/message/4z6z4zendcusdcnu ) -- its great for archival
> so I like those things :-)
OK, I'll try and draw up a propos
On Thu, 10 Apr 2008, James Carman wrote:
> That sounds more like something that would be a top-level-project,
> IMHO.
Possibly much longer term, if there was the interest to sustain it!
> I could see multiple modules in something like J2ME Commons. I'm sure
> there isn't a standard set of "things
Hi All
I've been chatting to a few people at ApacheCon about a j2me commons, and
they suggested I bring the idea to the dev list.
My idea was to have a commons library that implemented all the common
things you want to do for j2me, which have annoyingly been missed out of
the j2me spec, or are qu
38 matches
Mail list logo
