[jira] [Resolved] (DOSGI-162) Compilation errors when using OSGi core 4.3.0/4.3.1/5.0.0

["Christian Schneider (JIRA)" <ji...@apache.org>]

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

Christian Schneider resolved DOSGI-162.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5
         Assignee: Christian Schneider
    
> Compilation errors when using OSGi core 4.3.0/4.3.1/5.0.0
> ---------------------------------------------------------
>
>                 Key: DOSGI-162
>                 URL: https://issues.apache.org/jira/browse/DOSGI-162
>             Project: CXF Distributed OSGi
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>         Environment: Oracle JDK 1.7.0_17
>            Reporter: Amichai Rothman
>            Assignee: Christian Schneider
>            Priority: Minor
>             Fix For: 1.5
>
>         Attachments: fix_osgi_compilation_errors.diff
>
>
> When trying to compile against the OSGi core library releases 4.3.0, 4.3.1 and 5.0.0, there are several compilation errors. The fix includes:
> - cast null to String when calling BundleContext.getServiceReferences (an overloaded method was added, and passing null now causes ambiguity)
> - fix generic types and use of Properties (which extend Hashtable<Object, Object>), by using Dictionary<String, String> implemented as Hashtable<String, String> instead.
> - split between osgi.version and osgi.enterprise.version POM properties since the two have independent release versions (specifically, there are no enterprise 4.3.0/4.3.1 releases).
> The fix is backward-compatible, so compilation is successful on 4.2.0/4.3.0/4.3.1/5.0.0 with the patch applied. However, there are still 4 unit tests which fail in the later versions, but these are unrelated to the compilation errors and have to do with other dependency library versions (the patch does not change any versions). So consider this the first step.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira