You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Aaron Coburn (Jira)" <ji...@apache.org> on 2021/06/21 16:06:00 UTC

[jira] [Commented] (JENA-2121) Can't use jena-core, jena-iri in modular runtime-image

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

Aaron Coburn commented on JENA-2121:
------------------------------------

Jena releases jars with Automatic-Module-Name metadata, which should be sufficient.

I have used these Jena components for several years now in a Java 11-based JPMS build. I do not believe the solution is necessarily to modify the Jena code. Are you certain that your module-info.java file is complete?

Here is a reference: https://github.com/trellis-ldp/trellis/blob/main/components/jena/src/main/java/module-info.java#L24-L27

> Can't use jena-core, jena-iri in modular runtime-image
> ------------------------------------------------------
>
>                 Key: JENA-2121
>                 URL: https://issues.apache.org/jira/browse/JENA-2121
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: Core, IRI
>         Environment: Java 11
>            Reporter: Robin Tissot
>            Priority: Critical
>
> Hello,
> I'm trying to create a runtime-image to distribute an Java 11 application which is using jena-core and jena-iri using jlink but jlink command give me error "automatic module cannot be used with jlink: org.apache.jena.core".
> So I use moditect-maven-plugin to fix this error, this plugin consists of adding module descriptors to existing JAR files, and I created module descriptors of jena-core and jena-iri using jdeps command-line tool. This fix my error with jlink but now I have an error when launching the runtime-image: "java.util.ServiceConfigurationError: org.apache.jena.sys.JenaSubsystemLifecycle: module org.apache.jena.core does not declare 'uses' ".
> My guess is the solution should be adding a complete module-info.java file in jena modules.
> Here is a minimal project showing the problem : [https://github.com/Trobiun/JenaSample]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)