[
https://issues.apache.org/jira/browse/OLINGO-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ronny Bremer updated OLINGO-1565:
---------------------------------
Description:
When using Olingo v4 client libraries in any kind of J2EE web container, a lot
of issues arise when the underlying dependencies change. For instance, Jackson
seems to be a major component in Wildfly's J2EE subsystem, however, even the
latest Wildfly release 26..0.1 "only" features Jackson 2.12.
Are newer features really used inside of the Olingo client library or what is
the decision making process behind requiring the latest releases?
> what is the decision process to use newer versions of dependencies?
> -------------------------------------------------------------------
>
> Key: OLINGO-1565
> URL: https://issues.apache.org/jira/browse/OLINGO-1565
> Project: Olingo
> Issue Type: Question
> Affects Versions: (Java) V4 4.9.0
> Reporter: Ronny Bremer
> Priority: Major
>
> When using Olingo v4 client libraries in any kind of J2EE web container, a
> lot of issues arise when the underlying dependencies change. For instance,
> Jackson seems to be a major component in Wildfly's J2EE subsystem, however,
> even the latest Wildfly release 26..0.1 "only" features Jackson 2.12.
> Are newer features really used inside of the Olingo client library or what is
> the decision making process behind requiring the latest releases?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
