Hi all guys,
I am prototyping the Jackson support as described in CHAIN-76 and
found an elegant solution with ServiceLoader to support, via Jackson,
multiple format support without hardcoding them in the ConfigParser
code but rather loading available parsers at runtime.
Since [chain2] hasn't
I vote for going to Java 6. Java 6 is end of life in November, so it
seems a bit silly to support two end of life versions of Java. One
seems sufficient. That said - I may be breaking from the consensus
here at the Apache Commons.
-Elijah
On Mon, Aug 6, 2012 at 8:13 AM, Simone Tripodi
+1 to upgrade to Java 6.
On Mon, Aug 6, 2012 at 11:13 AM, Simone Tripodi
simonetrip...@apache.org wrote:
Hi all guys,
I am prototyping the Jackson support as described in CHAIN-76 and
found an elegant solution with ServiceLoader to support, via Jackson,
multiple format support without
+1 for Java 6 as well.
Matt
On Mon, Aug 6, 2012 at 10:59 AM, James Carman
ja...@carmanconsulting.com wrote:
+1 to upgrade to Java 6.
On Mon, Aug 6, 2012 at 11:13 AM, Simone Tripodi
simonetrip...@apache.org wrote:
Hi all guys,
I am prototyping the Jackson support as described in CHAIN-76
Democracy wins, long live Java6! :)
thanks for the feedbacks!
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Mon, Aug 6, 2012 at 6:08 PM, Matt Benson gudnabr...@gmail.com wrote:
+1 for Java 6 as
