Samael Bate created XMLCOMMONS-101:
--------------------------------------

             Summary: Where is the source for XML Commons External 
(xml-apis-ext)
                 Key: XMLCOMMONS-101
                 URL: https://issues.apache.org/jira/browse/XMLCOMMONS-101
             Project: XML Commons
          Issue Type: Task
            Reporter: Samael Bate
         Attachments: image-2024-10-18-15-41-50-371.png

This is related to XMLCOMMONS-99

I'd like to make a PR so that a future release of xml-apis-ext can support 
JPMS. It's used by so many Apache XML projects I rely on yet I can't pin point 
where the source is. 

I rely on xmlgraphics-commons, xmlgraphics-batik, xmlgraphics-fop, xalan-java, 
commons-beanutils, and commons-logging. In turn some of these depend on 
xml-apis-ext. I've made numerous pull requests to these projects but unless 
Commons External is updated to include an Automatic Module Name or be compiled 
with a more recent JDK and a module-info.java then the other dependencies won't 
be able to fully support JPMS. This is a blocker for me as I use jlink.


{code:java}
[WARNING] 
***********************************************************************************************************************************************
[WARNING] * Required filename-based automodules detected: 
[xml-apis-ext-1.3.04.jar]. Please don't publish this project to a public 
artifact repository! *
[WARNING] 
***********************************************************************************************************************************************
{code}

All of these are released by Apache. I'd like to contribute but am struggling 
to find out where to find the code. I don't mind it being git, subversion, or 
even cvs, as long as there's a way to create a PR or patch that can be reviewed 
and merged.

 !image-2024-10-18-15-41-50-371.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to