[jira] [Commented] (XALANJ-2784) JPMS: problem when using xalan-2.7.3 in modular build

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

Samael Bate commented on XALANJ-2784:
-------------------------------------

equally merging [https://github.com/apache/xalan-java/pull/195] so that Xalan doesn't result in `filename-based automodules` warning would also be helpful

> 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)