Do we help the community (lower footprint) when we switch from jodatime to java8 zoneddatetime? Op 27 jun. 2016 8:33 p.m. schreef "arno noordover [via Camel]" < ml-node+s465427n5784467...@n5.nabble.com>:
> I decided to implement the raised issue only for 2.18.0, because the > use-case for old dates in salesforce isn't very clear. > This decision was made on the fact that 2.18.0 didn't support jodatime at > all and this was a regression. > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://camel.465427.n5.nabble.com/camel-salesforce-component-date-time-issue-tp5784399p5784467.html > To unsubscribe from camel salesforce component date time issue, click here > <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5784399&code=YW5vb3Jkb3ZlckBnbWFpbC5jb218NTc4NDM5OXwxOTYxMzYyMjk2> > . > NAML > <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://camel.465427.n5.nabble.com/camel-salesforce-component-date-time-issue-tp5784399p5784469.html Sent from the Camel - Users mailing list archive at Nabble.com.
