Discussion:
[jira] [Created] (ISIS-1981) Eclipse: DataNucleus enhancer does see 2 different javax.jdo:jdo-api versions on class-path
Andi Huber (JIRA)
2018-09-05 05:17:00 UTC
Permalink
Andi Huber created ISIS-1981:
--------------------------------

Summary: 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
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)
Andi Huber (JIRA)
2018-09-05 09:32:00 UTC
Permalink
[ https://issues.apache.org/jira/browse/ISIS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604183#comment-16604183 ]

Andi Huber commented on ISIS-1981:
----------------------------------

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.
Post by Andi Huber (JIRA)
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)
Andi Huber (JIRA)
2018-09-05 09:33:00 UTC
Permalink
[ 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.
Post by Andi Huber (JIRA)
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)
Andi Huber (JIRA)
2018-09-05 09:34:00 UTC
Permalink
[ 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)
Andi Huber (JIRA)
2018-09-05 09:34:00 UTC
Permalink
[ https://issues.apache.org/jira/browse/ISIS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andi Huber closed ISIS-1981.
----------------------------
Resolution: Won't Fix
Post by Andi Huber (JIRA)
[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)
Andi Huber (JIRA)
2018-09-05 10:31:00 UTC
Permalink
[ https://issues.apache.org/jira/browse/ISIS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604249#comment-16604249 ]

Andi Huber commented on ISIS-1981:
----------------------------------

another workaround:

adding this to my project's pom.xml at the very top of the dependency list, forces the enhancer to load this jdo-api first
{code:xml}
<dependency>
<groupId>javax.jdo</groupId>
<artifactId>jdo-api</artifactId>
<version>3.1</version>
<scope>system</scope>
<systemPath>{$mvn-repository}\org\datanucleus\javax.jdo\3.2.0-m8\javax.jdo-3.2.0-m8.jar</systemPath>
</dependency>
{code}
Post by Andi Huber (JIRA)
[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)

Loading...