[
https://issues.apache.org/jira/browse/JENA-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366733#comment-17366733
]
Rob Vesse commented on JENA-2121:
---------------------------------
[~acoburn] So I think this issue is specific to the use case of using {{jlink}}
to create a minimised Docker image build.
It clearly is possible to do this since I know the sample [Fuseki2
Dockerfile|https://github.com/apache/jena/blob/main/jena-fuseki2/jena-fuseki-docker/Dockerfile]
does this.
But it may be the case that Automatic Module Names are insufficient for the
more general case
> 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
> Attachments: module-info.java
>
>
> 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)
