[ 
https://issues.apache.org/jira/browse/XALANJ-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18040389#comment-18040389
 ] 

Samael Bate edited comment on XALANJ-2823 at 11/24/25 10:21 PM:
----------------------------------------------------------------

Thanks, I've forked now and will make some pull requests soon. There seems to 
be a need to add a dependency to get some of these imports working. What jar 
are you adding to your classpath for 
{{{}org.apache.xpath.objects.ResultSequence{}}}? 

Are you building {{org.apache.xsl:xalan-java:jar:3.0.1-SNAPSHOT}} from a branch 
of Xalan and then adding it to your Eclipse project when working on 
xpath31_types? If so, it seems that the xalan-j_xslt3.0_mvn branch is also 
missing something as it has a dependency on {{Jlex:Jlex:jar:1.0}} which isn't 
available from mvn central or in the project repo


was (Author: singingbush):
Thanks, I've forked now and will make some pull requests soon. There seems to 
be a need to add a dependency to get some of these imports to working. What jar 
are you adding to your classpath for org.apache.xpath.objects.ResultSequence?

> 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)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to