You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Andi Huber (JIRA)" <ji...@apache.org> on 2018/09/05 09:34:00 UTC
[jira] [Updated] (ISIS-1981) [WONT-FIX] Eclipse: DataNucleus
enhancer does see 2 different javax.jdo:jdo-api versions on class-path
[ https://issues.apache.org/jira/browse/ISIS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andi Huber updated ISIS-1981:
-----------------------------
Summary: [WONT-FIX] Eclipse: DataNucleus enhancer does see 2 different javax.jdo:jdo-api versions on class-path (was: Eclipse: DataNucleus enhancer does see 2 different javax.jdo:jdo-api versions on class-path)
> [WONT-FIX] 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)