You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Ramesh Reddy (JIRA)" <ji...@apache.org> on 2016/03/31 14:54:25 UTC
[jira] [Issue Comment Deleted] (OLINGO-925) EdmxReference package
is in both commons-api and Server-api
[ https://issues.apache.org/jira/browse/OLINGO-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh Reddy updated OLINGO-925:
--------------------------------
Comment: was deleted
(was: I added OLINGO-925 as blocker for 4.2.0)
> EdmxReference package is in both commons-api and Server-api
> -----------------------------------------------------------
>
> Key: OLINGO-925
> URL: https://issues.apache.org/jira/browse/OLINGO-925
> Project: Olingo
> Issue Type: Bug
> Components: odata4-commons, odata4-server
> Affects Versions: (Java) V4 4.1.0
> Reporter: Ramesh Reddy
> Priority: Blocker
> Fix For: (Java) V4 4.2.0
>
>
> After the build, EdmxReference class is in both "commons-api" and "server-api" jar files. This leads to class loader issues when EdmxReference is used in the code.
> This is due to "bundle" package mechanism, depending upon how it configured, it will pull packages from other modules to be complete.
> The solution here is to use the distinct package names.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)