[
https://issues.apache.org/jira/browse/ISIS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604183#comment-16604183
]
Andi Huber edited comment on ISIS-1981 at 9/5/18 9:32 AM:
----------------------------------------------------------
Seems there is no fix to this issue on Isis' side.
However, as long working with DN-5 core plugin, this works for me:
replacing <maven-repo>\javax\jdo\jdo-api\3.1\jdo-api-3.1.jar with an empty jar.
was (Author: hobrom):
Seems there is no fix to this issue on Isis' side.
However, as long working with DN-% core plugin, this works for me:
replacing <maven-repo>\javax\jdo\jdo-api\3.1\jdo-api-3.1.jar with an empty jar.
> Eclipse: DataNucleus enhancer does see 2 different javax.jdo:jdo-api versions
> on class-path
> -------------------------------------------------------------------------------------------
>
> Key: ISIS-1981
> URL: https://issues.apache.org/jira/browse/ISIS-1981
> Project: Isis
> Issue Type: Bug
> Components: Core
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-M2
>
>
> Conflicting are javax.jdo:jdo-api:3.1 and javax.jdo:jdo-api:3.2-m8
> pom.xml files that declare dependence on javax.jdo:jdo-api should do so with
> scope *provided*.
> Only the jdo-datanucleus plugins should declare *test*- and *compile*-scoped
> dependencies.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
