Depends… If it’s a fix that should go back to 2.14 or earlier, it would need to 
be Java6.

For 2.15 stuff, I *hope* we can say Java7, but so far the poms and such haven’t 
been updated for Java7.   I’ve been kind of waiting for 2.14 to get out before 
really delving into that discussion.   :-)

Dan

On Sep 15, 2014, at 4:15 AM, Antoine DESSAIGNE <[email protected]> 
wrote:

> Hi Claus,
> 
> From now on, we can use the java7 features in the code ?
> (try-with-resource, etc...)
> 
> Antoine.
> 
> 2014-09-13 7:35 GMT+02:00 Claus Ibsen <[email protected]>:
> 
>> Java 7
>> 
>> On Fri, Sep 12, 2014 at 9:48 PM, rickaroni <[email protected]> wrote:
>>> Hiya,
>>> 
>>> Should I assume from this link that all Camel contribution code has to be
>>> Java 6 compatible?
>> http://camel.apache.org/what-are-the-dependencies.html
>>> <http://camel.apache.org/what-are-the-dependencies.html>
>>> 
>>> That is, I'd like to change a component such that Joda DateTime is
>> replaced
>>> by the new Java 8 OffsetDateTime.  Is it kosher to do that but provide a
>> JSR
>>> 310 backport via a maven dependency like this?
>>> 
>> http://mvnrepository.com/artifact/com.fasterxml.jackson.datatype/jackson-datatype-jsr310/2.4.2
>>> <
>> http://mvnrepository.com/artifact/com.fasterxml.jackson.datatype/jackson-datatype-jsr310/2.4.2
>>> 
>>> 
>>> Thanks,
>>> Rick
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> --
>>> View this message in context:
>> http://camel.465427.n5.nabble.com/Camel-contributions-which-Java-version-to-code-to-tp5756456.html
>>> Sent from the Camel Development mailing list archive at Nabble.com.
>> 
>> 
>> 
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> Email: [email protected]
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>> hawtio: http://hawt.io/
>> fabric8: http://fabric8.io/
>> 

-- 
Daniel Kulp
[email protected] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Reply via email to