[ https://issues.jboss.org/browse/WFLY-10279?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10279: ----------------------------------------- [~smarlow] If there's no existing place where a note about this would fit it seems kind of obscure and not particularly related to WildFly for us to document it. (Apache BSF 3.x, latest release 2013, doesn't even include this class. So we're talking old stuff.) Of course if the upstream of our xalan-j fork had this fixed we should port that. But they haven't done that. Perhaps we could provide a module-info.java via our fork. It seems a bit off to do that via what's basically a bug-fix fork though. I'm not sure if we've done that for other such things. [~ropalka] or [~dmlloyd] may know better. (I consider our spec API jars to be a different category from jboss/xalan-j.) I _assume_ a module-info.java would fix this as it would stop jar -d from trying to figure out the module description via code analysis. A module-info.java would not list org.apache.xalan.extensions.bsf.BSFManager as a provided service, both because the module doesn't provide it and because that string never represented a ServiceLoader service interface name; it was used for a pre-ServiceLoader mechanism for finding implementations of things. -- This message was sent by Atlassian Jira (v7.12.1#712002)