GitHub user jpullmann opened a pull request:

    https://github.com/apache/jena/pull/134

    Fix Jena initialization in OSGi environments

    This is a suggestion to fix errors in static initialization of Jena 3 in 
OSGi environments folowing the OSGi ServiceLoader Mediator spec. The 
appropriate manifest headers and a bundle activator were added: 
    
     
http://mail-archives.apache.org/mod_mbox/jena-users/201603.mbox/%3C2804-56ee5500-b-5266a380%40181641092%3E
    
    The original integration test (jena-osgi-test) was ineffective. Missing a 
runtime configuration the test methods did not run/never failed on my side. It 
works for Apache Karaf now. 
    
    Please install the uploaded, OSGi-fied dependency 
com.github.andrewoma.dexx:collection: 
    
    mvn install:install-file -Dfile=collection-0.4.0.jar 
-DgroupId=com.github.andrewoma.dexx -DartifactId=collection -Dversion=0.4.0 
-Dpackaging=jar
    
    and run the integration test: mvn -Drat.ignoreErrors=true clean 
integration-test
    
    If needed, I'll extend the test to cover other OSGi environments (Equinox 
etc.)
    
    
[collection-0.4.0.zip](https://github.com/apache/jena/files/202677/collection-0.4.0.zip)


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jpullmann/jena master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/jena/pull/134.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #134
    
----
commit 2462447f56660ddedff092deced1d0052765fc42
Author: Jaroslav Pullmann <[email protected]>
Date:   2016-03-29T15:56:12Z

    Fixed static initialisation issue in OSGi by adding SPI-related headers

commit 0ff9beb1122ffc1f2e5812972a81107f037c9e12
Author: Jaroslav Pullmann <[email protected]>
Date:   2016-04-04T14:23:36Z

    Jena-OSGi integration test updated, removed Xerces as embedded dependency

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to