[ 
https://issues.apache.org/jira/browse/JENA-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141262#comment-15141262
 ] 

ASF GitHub Bot commented on JENA-1139:
--------------------------------------

GitHub user stain opened a pull request:

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

    JENA-1139 workaround

    This workaround for JENA-1139 concatenates
    the content of the other Jena modules
    
`src/main/resources/META-INF/services/org.apache.jena.system.JenaSubsystemLifecycle`
    from jena-osgi's inlined modules `jena-core`, `jena-arq` and `jena-tdb`

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

    $ git pull https://github.com/stain/jena JENA-1139

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

    https://github.com/apache/jena/pull/126.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 #126
    
----
commit 2e0877898654d46e4d46efb0bcc3e84e0b94c7c1
Author: Stian Soiland-Reyes <[email protected]>
Date:   2016-02-10T17:31:13Z

    JENA-1139 workaround
    
    This workaround concatinates
    the content of the other Jena modules
     
src/main/resources/META-INF/services/org.apache.jena.system.JenaSubsystemLifecycle
    from jena-osgi's inlined modules jena-core, jena-arq and jena-tdb

----


> jena-osgi does not initialize all modules
> -----------------------------------------
>
>                 Key: JENA-1139
>                 URL: https://issues.apache.org/jira/browse/JENA-1139
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: OSGi
>    Affects Versions: Jena 3.0.1
>            Reporter: Stian Soiland-Reyes
>
> As discovered in TAVERNA-892 the jena-osgi of Jena 3.0.1
> seems to have not merged correctly 
> META-INF/services/org.apache.jena.system.JenaSubsystemLifecycle
> which breaks the new Jena initialization - only TDB is initialized - but TDB 
> depends on ARQ already being initialized (to get its context).
> {code}
> stain@biggie:~/.m2/repository/org/apache/jena/jena-osgi$ unzip 
> ./3.0.1/jena-osgi-3.0.1.jar 
> META-INF/services/org.apache.jena.system.JenaSubsystemLifecycle
> Archive:  ./3.0.1/jena-osgi-3.0.1.jar
>   inflating: META-INF/services/org.apache.jena.system.JenaSubsystemLifecycle  
> stain@biggie:~/.m2/repository/org/apache/jena/jena-osgi$ cat 
> META-INF/services/org.apache.jena.system.JenaSubsystemLifecycle
> org.apache.jena.tdb.sys.InitTDB
> {code}
> So basically only the last JenaSubsystemLifecycle file survives when  shading 
> jena-core, jena-arq, jena-tdb, jena-iri with Embed-Dependency and inline=true.
> The equivalent of the Maven Shade plugin's ServicesResourceTransformer would 
> be able to merge these.
> https://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html#ServicesResourceTransformer
> but I'm not sure how this can be done with the bundle plugin.  I guess it 
> could be overridden with its own src/main/resources/META-INF/services/ file 
> in jena-osgi as well - but then it needs maintenance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to