On Dec 8, 2010, at 2:10 PM, Haswell, Joe wrote:
> Coming from a Haskell background, I really miss non-strict semantics in Java,
> and it seems that functor's support for them is fairly limited (I do note
> that it exists). It'd be fairly easy to implement them either over existing
> functor i
Coming from a Haskell background, I really miss non-strict semantics in Java,
and it seems that functor's support for them is fairly limited (I do note that
it exists). It'd be fairly easy to implement them either over existing functor
interfaces or as a separate package.
Also, it seems that t
On 2010-12-08, Gump wrote:
> /srv/gump/public/workspace/apache-commons/collections/src/java/org/apache/commons/collections/functors/SwitchTransformer.java:[68,38]
> invalid inferred types for T; actual arguments do not conforms to inferred
> formal arguments
> required: org.apache.commons.collec
Hi Jörg,
What about using standard java.net.IDN algorithm decoding?
Bad things that it only available since java 1.6.
Also that java.net.URI using old rfc2396 for compatibility issues.
Please see
http://download.oracle.com/docs/cd/E17802_01/j2se/javase/6/jcp/mr2/#java.net
As i see it needed to c
Hi Alex,
Alexander Rytov wrote:
> Hi, guys
> How about url validation?
> How to do it accoring new rfc3986 and IDN(international domain name)?
> common-validation use only old rfc2396 and doesn't check IDN and IPv6
> urls.
Feel free to provide patches with unit tests.
- Jörg
-
Hi, guys
How about url validation?
How to do it accoring new rfc3986 and IDN(international domain name)?
common-validation use only old rfc2396 and doesn't check IDN and IPv6 urls.
--
Alex
I ran Clirr recently on 2.2 against 2.1
There are quite a few errors (see below)
However, I don't know if these affect binary compatibility for users -
perhaps all the affected code is internal use only?
ERROR: 5001: oacm.ArgumentOutsideDomainException: Removed
oacm.FunctionEvaluationException f
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-quartz has an issue affecting its community
integratio
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-scxml-test has an issue affecting its community integration.
This
Le 08/12/2010 00:10, Gilles Sadowski a écrit :
>>
>> I think we should push 2.2 out as fast as possible (i.e. before
>> Christmas) and concentrate the few cycles we have available to 3.0.
>
> +1
>
> And targetting spring for 3.0 ?
Yes, that would be nice.
Luc
>
>
> Gilles
>
> --
11 matches
Mail list logo