On 02/03/2025 05:21, Mukul Gandhi wrote:
Hi Alan,
Thanks for your reply.
On Thu, 27 Feb, 2025, 13:41 Alan Bateman, <alan.bate...@oracle.com> wrote:
If you are interested in contributing to the XML implementations
in the java.xml module then this would be welcomed. It's always
better to start small with bug fixes, test improvements and other
changes to get used to working in this project and build up
confidence that you are someone that is interested in maintaining
this area in the long term.
I think, I'll find writing Xalan-J XSL 3 specific code changes myself
in java.xml module of openjdk useful. Xalan-J XSL 3 code has also
required few changes to be made within, Xerces-J code as well (I think
to support XPath 3.1 function implementation for fn:deep-equal,
specifically for support of collation uris).
How should I start modifying openjdk's java.xml code? Do I need to
require building openjdk also to verify that nothing has gone wrong,
after modifying java.xml's code locally? Is it possible you may point
me to correct documentation for building openjdk?
Another approach I think may be to have me modify openjdk java.xml's
code locally and open a pull request for you all to verify and merge.
Any thoughts please?
The "Building the JDK" docs [1] has the build instructions, and the Open
Developers' Guide [2] has a good section on contributing.
Contribution an upgrade to XSL 3 is not a suitable first contribution.
That's a potentially JDK Enhancement Proposal (JEP) sized effort and
would require a huge amount of work from existing OpenJDK maintainers to
establish provenance, review, security audit, and test.
I realize you, and the others cc'ed, are experts in the XML field but
starting out here will require chopping wood and carrying water before
taking on anything significant. There are bugs and issues tracked in the
Java Bug System (JBS) in the "xml" component that may be suitable to
take on.
-Alan
[1] https://openjdk.org/groups/build/doc/building.html
[2] https://openjdk.org/guide/
