[
https://issues.apache.org/jira/browse/XMLCOMMONS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941346#comment-17941346
]
Samael Bate edited comment on XMLCOMMONS-101 at 4/6/25 10:31 AM:
-----------------------------------------------------------------
I just saw the svn url for https://svn.apache.org/repos/asf/xerces/xml-commons/
in a comment of
[XMLCOMMONS-90|https://issues.apache.org/jira/browse/XMLCOMMONS-90].
I'd really like to get some movement on making changes. Should a create patch
files or is anyone in ASF planning on a git migration?
[~ggregory] Do you know if there is any work being done currently on migrating
xml commons to github?
edit: Also, as it seems that svn is the latest src, when migrating please
include the patch I submitted on
[XMLCOMMONS-100|https://issues.apache.org/jira/browse/XMLCOMMONS-100]
was (Author: singingbush):
I just saw the svn url for https://svn.apache.org/repos/asf/xerces/xml-commons/
in a comment of
[XMLCOMMONS-90|https://issues.apache.org/jira/browse/XMLCOMMONS-90].
I'd really like to get some movement on making changes. Should a create patch
files or is anyone in ASF planning on a git migration?
[~ggregory] Do you know if there is any work being done currently on migrating
xml commons to github?
> 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
> Priority: Trivial
> 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]
