My apologies about the LocationLock, I did not commit any change to that. Perhaps my branch got out of date with master (Github didn't indicate anything weird so I didn't check properly)
Thanks for accepting the little workaround, I think it is the easiest option for now rather than fight Maven to do the wrong thing. I'll test the SNAPSHOT. On 10 Feb 2016 19:45, "ASF GitHub Bot (JIRA)" <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/JENA-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141430#comment-15141430 > ] > > ASF GitHub Bot commented on JENA-1139: > -------------------------------------- > > Github user afs commented on the pull request: > > https://github.com/apache/jena/pull/126#issuecomment-182525289 > > I tried to pull this and got changes to tdb/base/file/LocationLock > (possibly no actual change). What's happening? > > > > 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) >
