Samael Bate created XERCESJ-1786:
------------------------------------
Summary: Please move the XML API's Ext code to it's own git repo
Key: XERCESJ-1786
URL: https://issues.apache.org/jira/browse/XERCESJ-1786
Project: Xerces2-J
Issue Type: Wish
Reporter: Samael Bate
As per XMLCOMMONS-101 for some time I've been asking about the source for
xml-apis-ext as I'm keen to have a newer release that can work with JPMS. Today
I found that the source has been copied from svn into the same
[xerces-j|https://github.com/apache/xerces-j] git repo as xerces (in it's own
branch:
[tree/xml-commons-external|https://github.com/apache/xerces-j/tree/xml-commons-external]).
This isn't ideal, it's essentially making it hard for people to find and it'll
be hard to maintain moving forward. What's the strategy with this? How are
people expected to contribute? Should these _xml-commons-external_ and
_xml-commons-resolver_ branches just be maintained in place? Is there
documentation explaining how new contributors should work with the repo?
As far as I can tell, the current situation is: for me to make a change in
xerces I branch of main and make a PR to main when I'm done. Whilst for
_xml-commons-external_ I should check that branch out and branch off from there
making a PR back to _xml-commons-external_ when I'm done. Seems easy enough but
it would surely be easier for xml-commons-external to be in it's own repo.
Is there an Apache CI process for the xerces-j repo that builds all these
branches? The current GitHub Action doesn't cover these other branches:
[https://github.com/apache/xerces-j/actions]
It's not clear to me with the current setup how contributions to
_xml-commons-external_ will result in a potential new build being published to
mvn central
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-dev-h...@xerces.apache.org
