The only reason I can think of creating a separate repository is to provide a clean break from the Xalan code base. But, since XQuery is a superset of XPath, I imagine it will reuse the Xalan XPath code. Will it?
Do you plan on providing a standalone JAR for XQuery? If so, it seems it would depend on Xalan's JAR. If that's carrying too much weight, doesn't it make sense to break up Xalan into a Maven multi-module JAR with XPath as a standalone JAR? We're back to the Maven conversation I know... and I offer apologies for not having put more time in here. If the XQuery code will reuse any non-XPath functionality from Xalan then a plain dependency on Xalan is needed as mentioned above. My personal bias is to keep it all in the one git repo unless there is a compelling argument otherwise, and I don't know what that argument is here ;) HTH, Gary On Sun, Sep 6, 2026 at 7:17 AM Mukul Gandhi <[email protected]> wrote: > > Hello Xalan-J team, > I'm curious whether it'll be ok to develop a small XQuery > implementation, within Xalan-J? If yes, should we have a separate > GitHub Xalan-J code repos branch for this? > > For Xalan-J's XQuery implementation, lot of components available > within Xalan-J xslt3.0 implementation may be reused. > > I'm willing to start this activity. Anyone else, also willing to work > on this shall definitely be helpful. > > Any thoughts please? > > > -- > Regards, > Mukul Gandhi > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
