afs opened a new issue, #1804: URL: https://github.com/apache/jena/issues/1804
Currently, Jena 4.7.0, [Fuseki modules](https://jena.apache.org/documentation/fuseki2/fuseki-modules) are loaded during Jena start-up. The module itself is a single object with methods executed during the build step for Fuseki Main. There is a system-wide set of modules with code loaded using the Java ServiceLoader. Modules can be added without needing any Java code by placing jars on the classpath. A module is can be a shaded jar with necessary dependencies but it must not include the server Fuseki code. It is quite fragile to mange dependency exclusion. It is version sensitive. It is an extra step where errors can arise such as failure to supply the dependencies or get out of step with versions. This issue is for an additional way to use Fuseki modules; it does require Java code. By adding the ability to specific a list of modules to the build step, servers built from Java code can have modules which are not handled by ServiceLoader but are regular object instances. No special step to build a module jar; dependency management is all part of the development (maven/gradle). The default list would be the system-wide loaded list of modules - in other words, the default behaviour is as before. ### Are you interested in contributing a solution? Yes -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
