[jira] [Commented] (XALANJ-2823) implementation of xpath 3.1 partial function applications

"Mukul Gandhi (Jira)" <[email protected]>
Newsgroups gmane.text.xml.xalan.devel
Message-ID <[email protected]>
    [ https://issues.apache.org/jira/browse/XALANJ-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039145#comment-18039145 ] 

Mukul Gandhi commented on XALANJ-2823:
--------------------------------------

[~singingbush]

I think, that you may do these Xalan-J code refactoring if that improves Xalan-J's XSLT 3.0 test coverage.

The code for jar file xpath31_types-1.0.jar has EPL license, therefore I think, it cannot be hosted on Apache's code repos. The code for xpath31_types-1.0.jar is located here, https://github.com/xercesj/xalanj_xpath31_types.

If you wish to provide pr for changes to xpath31_types-1.0.jar, you'd need to provide pr on the repos https://github.com/xercesj/xalanj_xpath31_types. We'll then create a new jar xpath31_types-1.0.jar with new code and commit that to respective Xalan-J repos. For Xalan-J's consumption of new jar file xpath31_types-1.0.jar, changes to Xalan-J's code needs to be provided to related Xalan-J repos.

> implementation of xpath 3.1 partial function applications
> ---------------------------------------------------------
>
>                 Key: XALANJ-2823
>                 URL: https://issues.apache.org/jira/browse/XALANJ-2823
>             Project: XalanJ2
>          Issue Type: Task
>      Security Level: No security risk; visible to anyone(Ordinary problems in Xalan projects.  Anybody can view the issue.) 
>            Reporter: Mukul Gandhi
>            Assignee: Mukul Gandhi
>            Priority: Major
>
> I'm creating this jira issue to track, implementation of XPath 3.1 partial function applications within Xalan-J's XSLT 3.0 dev repos branch.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.