You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@metamodel.apache.org by "Kasper Sørensen (JIRA)" <ji...@apache.org> on 2015/08/25 09:01:45 UTC

[jira] [Closed] (METAMODEL-180) Avoid version conflict in jackson dependencies

     [ https://issues.apache.org/jira/browse/METAMODEL-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kasper Sørensen closed METAMODEL-180.
-------------------------------------
    Resolution: Won't Fix

Seemed this was not a conflict in MetaModel but in my applications other dependencies.

> Avoid version conflict in jackson dependencies
> ----------------------------------------------
>
>                 Key: METAMODEL-180
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-180
>             Project: Apache MetaModel
>          Issue Type: Bug
>            Reporter: Kasper Sørensen
>
> Using the latest (4.3.6) released Maven artifact MetaModel-full I see that the transitive dependencies of Jackson are in conflict. It seems jackson-annotations is v. 2.2.2 and jackson-databind is v. 2.4.13.
> At runtime this causes a NoClassDefFoundError. As a consuming application I thus have to do my own low-level dependency management which is doable but not a nice requirement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)