[
https://issues.apache.org/jira/browse/XALANJ-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883812#comment-17883812
]
Samael Bate commented on XALANJ-2784:
-------------------------------------
I've created a PR for this: [https://github.com/apache/xalan-java/pull/188]
I tested locally by building & installing locally a snapshot of xalan with the
dependency added. I was then able to build my project by depending on the
locally built XALAN instead of the 2.7.3 release (previously the build would
fail).
> JPMS: problem when using xalan-2.7.3 in modular build
> -----------------------------------------------------
>
> Key: XALANJ-2784
> URL: https://issues.apache.org/jira/browse/XALANJ-2784
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Affects Versions: 2.7.3
> Reporter: Samael Bate
> Priority: Major
> Labels: jpms, modularization
>
> Seeing the following error when using xalan in my app's module-info and
> running a build:
>
> {code:java}
> Can't extract module name from xalan-2.7.3.jar: Provider class
> org.apache.bsf.BSFManager not in module {code}
>
> This is perhaps because in _xalan/src/main/resources/META-INF/services/_
> there is a _org.apache.xalan.extensions.bsf.BSFManager_ service provider
> config that defines _org.apache.bsf.BSFManager_ as a service but the class
> isn't in the jar.
> Perhaps the released jar is missing a dependency on
> [commons-bsf|https://commons.apache.org/proper/commons-bsf]?
> {code:java}
> <dependency>
> <groupId>bsf</groupId>
> <artifactId>bsf</artifactId>
> <version>2.4.0</version>
> <optional>true</optional>
> </dependency> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
